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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding provenance ('discovered from GPS's public intelligence index pages') and a failure-mode disclosure ('if the issue hub cannot be read, issues_note says so in the payload'). That is real behavioral context beyond the structured hints, though nothing about pagination or result size.

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?

Front-loads the tool's identity, then filters, then the alternative, then a caveat, in five short sentences. Every sentence carries distinct information with no restatement of the name or annotations.

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?

With no output schema, the description does the work of explaining the payload shape at least partially, naming the `issues_note` field and pointing to get_page for full content. It does not enumerate the listed fields themselves (slugs, titles), which is a small residual gap for a discovery tool.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it does: `kind` accepts 'facility' or 'issue' (a constraint the schema lacks entirely, with no enum) and `contains` filters on the slug. It adds genuine meaning beyond the bare string types, though `contains` matching rules (substring vs. exact) remain unspecified.

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 GPS intelligence briefings') and immediately scopes it to two subtypes ('per-facility and per-issue analyses'). It is clearly distinguishable from the read sibling get_page, which it explicitly names as the full-content path.

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?

Gives a clear when-to-use signal by routing the agent to get_page() for full reads and showing a concrete example path. It lacks explicit exclusions or a 'use this when you only need to discover slugs' statement, so it stops just short of a 5.

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