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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds that it pulls everything 'in one call', is a 'free discovery magnet', and mentions alternative behavior of Probe/Instant. However, phrases like 'LEGACY OFF TABLE' and 'taste-only' are cryptic and not explained, reducing the practical transparency beyond the annotations.

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 description is front-loaded with the main purpose and fairly brief. However, it is fragment-heavy and includes unexplained jargon ('Pilot Challenge Exact $100 wealth unlock', 'LEGACY OFF TABLE', 'taste-only'), making it less clean and structured than ideal.

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 zero-parameter, read-only tool with an output schema and good annotations, the description provides a usable but incomplete context. Key terms like 'Pilot Challenge Exact $100 wealth unlock' and 'LEGACY OFF TABLE' are not defined, and there is no explicit statement of when to invoke this tool versus related siblings.

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?

The tool has 0 parameters and schema coverage is 100%, so there is no parameter surface for the description to clarify. The 0-parameter baseline of 4 applies, and the description adds no conflicting or misleading parameter information.

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 uses a specific verb ('Pull') and identifies concrete resources ('ranked open DENYs + Pilot Challenge Exact $100 wealth unlock', 'Denial Exchange inventory'). This makes the main function clear, but it does not explicitly contrast with sibling tools like sqlguard_denials or sqlguard_challenge, so it stops short of a 5.

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?

The description implies usage as a 'Free discovery magnet' and mentions that Probe remains free/not authorized and Instant remains taste-only, giving some comparative context. However, it never explicitly states when to use Gravity versus alternatives or lists exclusions, leaving usage guidance implied rather than direct.

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