Get rank check result

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

Annotations only declare a safe read, but the description adds substantial behavioral context: the error_code taxonomy with its stable values, which of those errors are retryable, and the null-position semantics tied to coverage level. This is exactly the kind of retry/semantics disclosure annotations cannot carry.

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?

The retrieval action is front-loaded in the first sentence, followed by tightly packed interpretation rules with no filler. It is dense to the point of being telegraphic in places, but every clause carries an operational rule an agent would otherwise have to guess.

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 takes on the burden of explaining return semantics and does so for status, observation_completeness, position null, and error_code. It is close to complete, though it never sketches the overall response shape or confirms what fields accompany a successful result.

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% for both parameters, so check_id and project_id are already documented in the schema. The description restates check_id lookup but adds no format, scoping, or cross-project meaning beyond it, matching the baseline for schema-complete tools.

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 ('Get one rank check result by check id'), so the agent knows it retrieves a single result object keyed by check_id. However, it never differentiates itself from the sibling get_rank_check_run / list_rank_check_runs, which is exactly the ambiguity an agent faces when picking among these near-identical names.

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?

Gives concrete interpretation conditions ('Read status and observation_completeness before interpreting position null') and an explicit action rule ('retry only for provider_rate_limited or provider_transient'), which is real when-to-use guidance. It stops short of naming an alternative tool or stating when this result lookup is preferred over fetching a run.

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