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

Annotations already establish readOnly/non-destructive/closed-world, and the description goes beyond them by disclosing the fallback path: when no receipt exists it returns scoringStatus and the initial Emerging archetype for registered users. That edge-case behavior is genuinely useful and not derivable from 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?

Two sentences, front-loaded with the primary purpose and the fallback second, which is a sensible ordering. The prose is dense and stuffed with undefined jargon terms that dilute signal rather than sharpen it.

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 bears the full burden of explaining return values, and it does attempt to enumerate them (policy, identity, exact/display points, Quality breakdown, scoringStatus, archetype). But the terms are domain-specific and undefined, so an agent cannot fully predict the response shape or interpret the fields.

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 0%, so the description must carry the load; it clarifies that 'handle' is a GitHub handle, which adds real meaning about the identifier's source. However it gives no format, casing, or validation details, so the parameter remains only partially specified.

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 gives a verb ('Return') and a resource ('the selected policy receipt'), but the resource is described almost entirely in opaque domain jargon ('policy receipt', 'v7.4 or v7.5 recorded activity', 'Quality breakdown', 'Emerging archetype'). It also does not distinguish itself from close siblings like get_impact_history or find_profile, so an agent cannot confidently pick it apart from the alternatives.

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?

There is no explicit when-to-use statement and no mention of alternatives among the many siblings (get_impact_history, find_profile, compare_profiles). The only conditional guidance is the degenerate-case fallback ('When no receipt is drawable'), which describes behavior, not invocation context.

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