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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the scope 'literature' but does not disclose additional behavioral traits such as result structure or execution details, so it provides only marginal value beyond annotations.

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 extremely concise with only two words, which is efficient but under-specified. While it is front-loaded and waste-free, it lacks the detail expected for a tool with a rich schema and many siblings, making it merely average rather than exemplary.

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 having a detailed schema and strong annotations, the description leaves out essential context for selecting this tool among many similar siblings. It does not clarify the literature scope, how it differs from the 'literature' or 'search_within' tools, or any contextual use case. The output schema covers return values, but selection guidance is missing.

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?

The schema has 100% description coverage for all five parameters, including query syntax, pagination, and sort options. The description adds no parameter-level meaning, so it neither enhances nor detracts from the schema's already complete documentation.

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 'Literature search.' clearly states the action (search) and resource (literature), making the core purpose understandable. However, it lacks any scope detail and does not differentiate from sibling tools like 'literature' or 'search_within', so it falls short of a perfect 5.

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?

There is no guidance on when to use this tool versus alternatives. The description offers no context about use cases, prerequisites, or exclusions, leaving the agent to infer applicability from the name and schema alone.

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