Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnlyHint, idempotentHint, etc.), the description adds behaviorally meaningful details: no API key required, IP-based rate limiting for unauthenticated callers, AND-combination of filters, return of summaries without bodies, and empty array as a non-error signal. This goes well beyond what annotations and schema provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact yet information-dense: first sentence sets scope, second establishes use case, third handles exclusions and edge behavior, fourth covers technical details. Every sentence earns its place with no padding or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite not having an output schema, the description discloses return shape (array of article summaries), absence of bodies, and empty-array semantics. Combined with 100% schema coverage, the tool is fully specified for querying, filtering, and understanding results, making for complete contextual coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that filters combine with AND, which clarifies interaction between q, tag, and author – a semantic not present in the schema property descriptions. This pushes the score slightly above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Search PUBLISHED articles across all of Misar.Blog, including other creators' work' – a specific verb, resource, and scope that leaves no ambiguity. It also clearly distinguishes itself from list_my_articles by stating what it never returns, providing strong sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names use cases ('discovery, research, and competitive reading') and gives a concrete alternative: 'reach for list_my_articles when you want your unpublished work.' Also directs users to get_article for full text, which provides clear guidance on when to use which tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.