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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the return content (badges, streaks, level, health score) but does not disclose any additional behavioral traits such as response format, performance implications, or authentication requirements. With annotations covering the main safety aspects, this is adequate but not rich.

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 no fluff. It front-loads the purpose and then clarifies the return data. Every word contributes to understanding the tool's function. It is appropriately sized for a zero-parameter read operation.

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 simple read-only tool with no parameters and no output schema, the description is mostly complete. It specifies what data is returned, though it could be more explicit about the exact structure of the response (e.g., field names) or edge cases like empty gamification data. However, given the simplicity, it meets the minimum bar for an agent 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?

The tool has zero parameters, so the schema provides no parameter documentation. Per the calibration, the baseline for 0 params is 4, and the description doesn't need to explain parameters. It correctly focuses on the output content, which is the only relevant semantic 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 clearly states the verb 'get' and the resource 'gamification summary', listing the specific components (badges, streaks, level, health score). This distinguishes it from sibling tools that focus on individual aspects, such as get_budget_streaks or get_financial_health_score, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. There are sibling tools like get_points_and_level, get_budget_streaks, and get_financial_health_score that overlap in content. An agent would have to infer that this is the aggregated view without any explicit recommendation or differentiation.

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