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

Annotations already declare readOnlyHint and openWorldHint, and the description adds output-level behavior beyond that: claims are labeled FACT/DERIVED/UNKNOWN with evidence ids, and the tool explicitly declines price advice or safety verdicts. That taxonomy is genuinely useful context an agent cannot get from the annotations, though latency, coverage limits, or rate behavior are not mentioned.

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?

Ten parameters and seven capabilities are compressed into roughly 90 words with no filler sentences; the lead questions and the capability list are front-loaded. The telegraphic parenthetical style is dense but each clause maps to a real routing or parameter decision.

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 an output schema present, the description need not explain return values, and it does add the claim-labeling taxonomy and scope exclusions. However, for a 10-parameter, 7-capability dispatcher with heavy sibling overlap, the missing parameter semantics and absence of sibling routing leave real gaps an agent must resolve by trial.

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 0% across 10 parameters, so the description carries the burden. It documents the most important ones (q content types, days 1-30, projects 2-4, full capability enum) but leaves limit, types, detail, and building entirely unexplained, so half the surface remains undocumented.

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 communicates what the tool produces: a single cited answer to research questions about a Robinhood Chain project, with an enumerated capability list (research_project, what_changed, verify_project, compare_builders, unknowns) that clarifies its scope. It is not a clean verb+resource statement and never mentions the 7 sibling tools, so an agent must infer the boundary versus get_changes, find_projects, or get_evidence on its own.

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?

It gives per-capability conditions in parentheses: q accepts a name/$TICKER/address/project slug (a shared name lists candidates), what_changed takes a project or chain over 1-30 days, compare_builders takes 2-4 with no winner. It also states an explicit exclusion, 'Not price advice or a safety verdict,' which acts as a when-not. It falls short of naming the sibling alternatives that cover overlapping ground.

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