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

Annotations already declare readOnlyHint=true, so the description builds on that by adding the fallback behavior when no drawable receipt exists, and lists the possible scoringStatus values. It also specifies the version (v7.2) and the headline fields, which adds context beyond the annotations without contradicting them.

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 the primary purpose and headline fields front-loaded, followed by the fallback behavior. Every phrase adds value, and there is no redundant or filler content.

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?

Given the simplicity (1 parameter, read-only annotation, no output schema), the description covers the essential return values (displayScore, displayTier) and the fallback (scoringStatus with its possible values). It lacks a detailed structure of the response object, but this is adequate for a tool with a single parameter and no complex schema.

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?

With schema description coverage at 0%, the description must clarify the handle parameter. It does mention 'GitHub handle', which adds minimal context, but does not specify format, pattern, or validation rules. For a single simple string parameter, this is a slight improvement over the schema but still limited.

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 'Return' and resource 'current v7.2 receipt for a GitHub handle', making the tool's purpose clear. It mentions the headline fields (displayScore, displayTier) but does not explicitly differentiate from siblings like get_impact_history or find_profile, though the 'current receipt' phrasing implies a distinct temporal scope.

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 does not provide guidance on when to use this tool versus alternatives such as get_impact_history or find_profile. It only describes the tool's behavior and fallback condition (scoringStatus), but no explicit when-to-use or when-not-to-use criteria.

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