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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds useful context about the search scope and that results are summaries tied to get_doc_page, but it does not go deeper into rate limits, pagination, or exact result structure beyond the available output schema.

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 sentences with no filler, and the most important information ('search every page', 'use first when you do not know') is front-loaded. Every sentence earns its place.

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?

With a complete input schema, an output schema, annotations, and only two simple parameters, the description covers the key operational context: what gets searched, what is returned, and how the result connects to get_doc_page. Nothing critical 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?

Schema description coverage is 100%, so both 'query' and 'limit' are already documented in the schema. The description does not add new parameter-level meaning but reinforces that 'query' is the key search input; this meets the baseline but does not exceed it.

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'), the resource ('every page of agent-manager.dev'), and the fields searched ('title, description and section'). It also explains the return shape (page summaries with slugs), which clearly differentiates it from get_doc_page and list_doc_pages.

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 says to use this first when the agent does not already know which page answers the question, which gives clear when-to-use guidance. It also implies the alternative path by noting the slug get_doc_page takes, though it does not explicitly state when not to use it.

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