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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context such as error handling, response format, or side effects. Given the annotations, the bar is lower, and the description meets the minimum but does not enrich beyond the basic operation.

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?

A single, concise sentence with no redundancy. The core information (verb, resource, scope) is front-loaded and every word is necessary.

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 single-parameter getter with annotations covering safety, the description is sufficient. It lacks details on return format or not-found behavior, but given the low complexity and the presence of sibling tools, it is complete enough for an agent to call correctly. Minor gap is the absence of error handling notes, which are not critical here.

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 schema describes the id parameter fully ('Badge rule id') with 100% coverage. The description adds no additional meaning about the parameter beyond what the schema provides. Baseline of 3 applies due to high schema coverage.

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 'Fetch a single badge rule by id' clearly states a specific verb (fetch), resource (badge rule), and the distinguishing scope (single, by id). This differentiates it from list_badge_rules, which would return multiple rules. No ambiguity.

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 the tool is for retrieving a single badge rule when an id is available, but it does not explicitly mention alternatives like list_badge_rules for multiple rules or create/update/delete for mutations. The guidance is implied through the singular scope and id parameter, but lacks explicit when-to-use vs. when-not-to-use guidance.

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