Get author

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

The description accurately reflects the readOnlyHint annotation (read-only fetch), and adds useful context about optional inclusion of library items. It does not contradict annotations and discloses safe, non-destructive behavior.

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 a single, front-loaded sentence that concisely captures the tool's core function and optional capability, with zero wasted words.

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 has a simple read operation with 4 well-documented parameters and no output schema, the description is largely complete. It covers the main behavior, and the schema handles parameter details. Slightly less complete in not explaining return values, but acceptable for a straightforward fetch.

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% with detailed parameter descriptions (e.g., detail enum explaining compact vs full, library_id restricting items). The description adds minimal extra meaning beyond the schema, but the schema itself is rich, so baseline 3 is adjusted to 4 for the value the description provides in signaling optional item inclusion.

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 fetches a single author and optionally includes library items. It uses specific verbs ('fetches') and resources ('author', 'library items'), and distinguishes itself from siblings like list_authors (bulk listing) by focusing on a single author 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?

The description implies usage for fetching an individual author, but does not explicitly state when to use this vs. list_authors or other tools. No alternatives or exclusions are mentioned, though the context is clear from the purpose.

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