get_cached_docs

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

Adds auto-caching behavior beyond annotations, which indicate readOnlyHint and openWorldHint. Could detail caching lifecycle but sufficient for basic understanding.

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?

Three concise sentences, no wasted words. Front-loaded with primary action.

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?

Adequately describes purpose, behavior, and prerequisites. Missing expected return format for a search tool, but low complexity reduces gap.

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 covers all 3 parameters with descriptions. Description does not add additional semantic value beyond matching 'keyword' to 'query' parameter.

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?

Clearly states it searches locally cached Rosetta CLI docs for a keyword. Distinguishes from sibling tools like search_rosetta_web_docs by specifying local cached nature and CLI focus.

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?

Implies usage for looking up command-line flags or parser info, and requires local installation. Lacks explicit alternatives or when-not-to-use but provides clear context.

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