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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral constraint — that matching is on title (not full text) and limited to the TAAFT catalog — but says nothing about result volume, ranking, or the limit cap's effect.

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?

A single front-loaded sentence with no filler: verb, corpus, resource, and matching dimension in one pass. Nothing to trim, nothing buried.

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?

An output schema exists, so return-value explanation is not needed, and annotations cover safety. However, for a search tool the description omits sibling routing (get_paper vs. search_papers) and any note on the uncovered limit parameter, leaving a couple of practical gaps.

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 50%: 'query' is documented and 'limit' is not documented anywhere. The phrase 'by title' adds meaning to query beyond the schema (title-oriented matching rather than free-text), but the undescribed limit parameter (default 20, max 50) is left entirely to the agent to infer.

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?

States a specific verb (Search) and resource (papers) scoped to the TAAFT catalog, and adds the search dimension ('by title'). It is distinguishable from get_paper (fetch by id) implicitly, but it never names siblings or contrasts search vs. retrieval.

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 statement of when to use this tool versus the sibling get_paper or the other search_* tools. Usage is only weakly implied by the tool name and the phrase 'by title'; no exclusions or alternatives are offered.

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