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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that ALL statuses (open, resolved, dismissed) are returned rather than a filtered set. It does not disclose pagination, result ordering, or how many issues come back, leaving a nontrivial gap for a list 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 well-formed sentence with no filler, and the resource and scope are front-loaded. It is appropriately sized, though it could carry a bit more without waste.

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 read tool with read-only annotations, the essentials are present. But with no output schema and no description of returned fields, pagination, or ordering, an agent still lacks behavioral detail it would need to consume results reliably.

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 is one parameter with 0% schema description coverage; the description implicitly ties it to an organization via 'an organization's', which maps to organizationId. It adds no format, validation, or source-of-id detail beyond that, so it only partially compensates for the undocumented schema.

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 gives a specific verb (list) and resource (authentication issues) scoped to an organization, and clarifies the statuses covered (open, resolved, dismissed). That's clear purpose, though it doesn't distinguish it from anything in particular since the sibling tools are unrelated CRUD/org tools.

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?

Usage is implied by the single required organizationId — an agent can infer it lists issues for one org. However, there's no explicit guidance on when to use this versus other retrieval paths, no prerequisites, and no statement about what happens if the org has no issues.

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