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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context by stating the spec is 'Generated from the live scoring config', indicating the data is dynamic and reflects current configuration. It also lists the exact fields the agent can expect, which goes 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 two sentences with zero filler. The first sentence front-loads the main content list, and the second adds a single relevant note about the data source. Every phrase earns its place, making it both concise and structured.

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 read-only, zero-parameter tool with no output schema, the description fully covers what an agent needs: it lists the complete set of information returned (thresholds, limits, unlocks, points, bonus, mechanics) and notes the source freshness. No critical details are missing for correct invocation.

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 zero parameters, so the schema coverage is trivially 100%. The description correctly avoids discussing parameters. Per the rubric, a 0-parameter tool earns a baseline of 4, and no additional parameter explanation is needed.

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 states a specific verb ('get') and resource ('trust-ladder spec'), and enumerates the exact content (score thresholds, rate limits, unlocks, points per action, AI-nativeness bonus, upgrade mechanics). This clearly distinguishes it from the sibling 'get_trust_signal', which likely returns a per-user signal rather than the ladder configuration.

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 gives clear context: it returns the complete ladder spec, so an agent understands when to call it (when it needs the ladder's scoring rules). It does not explicitly name alternatives or exclusions, but the specificity of the content makes the usage intent obvious. A minor omission is the lack of a direct 'use this instead of X' note.

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