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

Annotations cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description needn't restate that. It adds genuine value by disclosing the return shape — candidate methods with when-to-use, assumptions, R/Python packages, and library sections — which is important since no output schema exists.

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?

Two sentences, each earning its place: the first names the domains and purpose, the second covers inputs and outputs. No repetition of the title or annotations, and the purpose is front-loaded.

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 no output schema, the description carries the return-value burden and does so adequately, while the fully covered schema handles parameters and annotations handle safety. Nothing an agent needs to call this correctly 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 question, limit, and language are already documented in the schema, making 3 the baseline. The description adds meaning by explaining what the 'question' parameter should contain (setting plus treatment assignment), but says nothing about limit or language.

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 (recommend) and resource (statistical/econometric/causal inference/ML methods) scoped to a research question. It is clearly distinguishable from siblings like search, fetch, get_code, and cite, which do retrieval rather than method recommendation.

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?

Tells the agent exactly what context to supply (question, data structure such as cross-section/panel/time series/experiment, treatment assignment, outcome), which is practical invocation guidance. It does not name exclusions or alternative tools, but no sibling appears to overlap this function, so the gap is minor.

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