get_badges

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

With no annotations provided, the description carries the full behavioral burden. It correctly implies a read-only operation with no inputs and no side effects, which is accurate for this tool. It adds useful context about what is included (earned vs. in-progress badges, points, dates) but does not disclose pagination, freshness, or error behavior—minor for a simple no-param read tool.

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 a single, information-dense sentence with no wasted words. It front-loads the resource and distinguishes the two result categories. Given the tool's zero parameters, this size is appropriate.

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, the description is largely sufficient: it defines the output scope and requires no input. The presence of an output schema reduces the need to document return values. However, it lacks any guidance on how badges relate to other achievement-style tools (e.g., get_goals) or any note on update frequency.

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?

There are zero parameters in the schema, so schema description coverage is trivially 100%. Since the tool requires no inputs, there is nothing for the description to clarify beyond confirming it takes no arguments, which the schema itself already makes clear.

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 ('get') and resource ('badges'), and clearly distinguishes two output categories: badges earned and badges in progress. It adds point and date details that go beyond a bare restatement of the title. However, it does not explicitly distinguish itself from the sibling get_goals or get_progress_summary, which could overlap in intent.

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 this is a read-only, no-parameter query for badge status, which an agent can infer from the zero-parameter schema and the absence of any side-effect language. However, there is no explicit when-to-use guidance or mention of alternatives among the many sibling get_* tools.

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