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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds useful breadth-of-return context (confidence values, ranges and units, evidence count) that helps an agent judge payload richness. It says nothing about failure behavior for an invalid UUID/slug or about response size, which is the remaining behavioral gap.

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 one-line purpose, then parameter guidance, then the return inventory. Every section maps to a decision the caller must make, and the parenthetical examples are the only non-essential words. No filler or restatement of the title.

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?

For a single-parameter read tool with a full output schema and four annotations, the description covers purpose, identifier semantics, discovery path, and payload shape. An agent has everything needed to select and invoke it correctly; the only omission, invalid-identifier error behavior, is minor given the search-tool pointer.

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 coverage is 0% and the single parameter has no schema description, so the description must carry the meaning — and it does, defining the parameter as "UUID or slug" with three concrete example values. The pointer to search_bgi_measures for discovering valid slugs is genuinely additive. It does not state format constraints (case sensitivity, URL-encoding, whitespace) for the slug.

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?

Opens with a specific verb and resource ("Get full detail for one BGI measure") and immediately enumerates the payload domains: performance, costs, scores, constraints. The singular scope ("one measure") cleanly separates it from search_bgi_measures and the ranking/comparison siblings.

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 routes the agent to search_bgi_measures when a valid slug is unknown, which is the main selection hazard for this tool. It does not state exclusions (e.g. when to use compare_measures or get_parameters instead of the full detail blob), so it stops short of full when/when-not guidance.

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