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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context: only customer-defined rules are returned, analyzer-sourced badge types are excluded, and a dashboardUrl is included.

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 tight sentences front-load the purpose and field list. The exclusion note earns its place and the dashboardUrl detail is useful, not padding.

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-param read-only listing, it covers what is returned, what is excluded, and the dashboard URL. It doesn't specify ordering or pagination, but that is a minor gap for such a scoped operation.

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?

No parameters exist, so the empty schema is complete with 100% coverage. Baseline 4 applies because the description has no parameter details to compensate for.

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?

States a specific verb and resource: list the current customer's badge rules. Enumerates returned attributes and explicitly distinguishes from analyzer-sourced badges, making it hard to confuse with get_badge_rule or list_escalation_rules.

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?

Explicitly scopes to the current customer and tells agents not to expect analyzer-sourced badges here. It doesn't name an alternative tool or state when to prefer get_badge_rule, so it falls short of full explicit routing.

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