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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful content about what a record includes, but says nothing about pagination, the limit cap, or the default status filter behavior — gaps the schema only partly fills.

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 core action and the usage trigger, followed by a documentation link. Nothing is padded, though the bare API reference URL adds little to selection or invocation.

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 sketch the returned fields, which helps. But for a 6-parameter filtered-list tool it omits any discussion of the filterable dimensions or result limits, leaving the invocation contract under-explained.

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?

Six parameters with only 33% schema description coverage, and the description mentions none of them. It gives no hint that results can be filtered by project, client, or status, or that a limit applies, so the agent must reverse-engineer filtering from the schema alone.

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 (Read) and resource (known issues on a project), and enumerates what each record contains: blockers from external systems, severity, status, and fixing tasks. This cleanly separates it from the write siblings log_project_issue and update_project_issue.

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 an explicit trigger: read before starting work to avoid re-discovering or duplicating a known problem. That is actionable context, though it names no alternative tool and states no when-not condition.

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