Find Author

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

Describes matching methods (embedding similarity for topics, fuzzy matching for names) and details the return structure for both modes. Annotations already indicate readOnlyHint, and description adds behavioral context without contradiction.

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?

Single coherent paragraph, front-loaded with mode distinction, efficient wording, no redundancy. Every sentence adds value.

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?

Given the tool's two modes, four parameters, and existence of an output schema, the description adequately covers both modes' usage, return values, and parameter constraints without being overly verbose.

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%, baseline 3. Description adds value by explaining mode-specific applicability of parameters (e.g., field and limit for q-mode only) and providing examples, but does not add deep semantic nuance beyond schema.

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 it is a two-mode tool (search by topic/name or lookup by ID), replaces two other tools, and distinguishes its function from siblings like co_author_graph.

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 instructs to provide exactly one of q or id, and notes that field and limit apply only to q-mode. Also mentions that IDs come from q-mode or co_author_graph.

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