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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (title, path, summary, excerpt around matching text) and the follow-up workflow (read_doc + cite url), though it says nothing about ranking or pagination limits.

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?

Front-loaded with the verb and parallel structure across three short paragraphs (what / when / params), with no wasted sentences. The long parenthetical enumerations of doc topics and PIPs are dense but earn their place by signalling corpus coverage.

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?

No output schema exists, and the description compensates by describing the result fields and the read_doc handoff for full content. Combined with explicit usage criteria and query examples, an agent has everything needed to call and follow up correctly.

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 the baseline is 3; the description goes further by giving concrete query examples ('mining pool setup', 'how does the fee estimator work') and restating the kind values, which helps the agent phrase inputs. It does not clarify the limit parameter, which is fully handled by the 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?

States a specific verb and resource ('Searches the official Parallax documentation... and the Parallax Improvement Proposals') and enumerates the topical coverage so the agent knows exactly what corpus is searchable. It also distinguishes itself from the sibling read_doc by describing search-vs-read roles.

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 when to use it ('whenever a question is about how Parallax works or how to do something with it') and gives the rationale (Parallax diverges from Ethereum/Bitcoin, so don't answer from general knowledge). It also routes to the alternative: use read_doc to read a page in full and cite its url.

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