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

With no annotations, the description carries the full behavioral burden. It discloses deduplication, filter support, and engine constraint, but lacks details on edge cases (e.g., behavior when both author_id and author_name are provided) and any mention of output structure or pagination. This is adequate but not rich on behavioral traits.

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 dense and information-packed, with the main purpose front-loaded. Each sentence adds value, but the filter list and engine note make it slightly long. It is still concise given the complexity, with no filler.

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?

For a tool with six optional parameters and an output schema, the description provides good context: traversal purpose, filter syntax, and engine requirement. It does not cover all conceivable edge cases (like parameter conflicts), but it gives enough for an agent to invoke it correctly in most scenarios. Slightly incomplete due to lack of limit semantics.

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 description coverage is 0%, so the description must compensate. It explains author_id, author_name, candidate_index usage, filters syntax, and engines constraint. However, it does not describe the 'limit' parameter, which remains ambiguous. Overall, it adds significant semantic meaning beyond the raw schema, though one param is left undocumented.

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 clearly states the tool's function: 'Expand one author into a deduplicated paper list.' It uses a specific verb ('expand') and resource ('author into paper list'), and explicitly distinguishes itself as the 'main author->paper traversal tool' from sibling tools like scholarfetch_author_candidates. This makes its purpose unambiguous.

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?

The description provides explicit usage instructions: when to use author_id vs author_name plus candidate_index, specifically mentioning the prior use of scholarfetch_author_candidates. It also gives a complete list of supported filters and a critical constraint for the 'engines' parameter, which effectively communicates when and how to use the tool.

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