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

Annotations already declare the safe/read-only/idempotent profile, and the description goes further by enumerating the three possible `status` values and what each means, including the guarantee that a position is never fabricated and no confidence score is invented. That is substantive behavioral disclosure beyond the structured fields.

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 core purpose and the two modes, and every sentence carries routing or return-value information. The status enumeration is dense with em-dash parentheticals but does not waste words; slightly verbose packaging is the only cost.

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?

There is no output schema, so the description must carry return semantics itself, and it does: it explains both the list-mode result and the per-config check result with its status vocabulary. For a two-parameter read tool, an agent has everything needed to call it 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%, and the description's account of configId (present = latest check, absent = list all configs) essentially restates what the schema property text already says. It adds no syntax, format, or constraint detail for either parameter, so the baseline 3 applies.

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+resource ('Read-only access to local pack rank check configs and their latest check') and spells out the two operating modes keyed on configId. It explicitly contrasts itself with get_local_rank_grid (organic rank for a domain vs. local pack for a business), so an agent can distinguish it from the nearest sibling without opening a schema.

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 explicit when-to-use routing: use get_local_rank_grid for organic rank across a geo-grid, use create_local_pack_rank_config to make a config, and run_local_pack_rank_check to produce a new check. The condition selecting each alternative is stated rather than implied.

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