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

No annotations are provided, so the description carries the full behavioral burden. It does add real value by disclosing the underlying call (GET /api/0/projects/{org}/{project}/issues/?query=is:unresolved), which confirms this is a read-only operation and that the query is hard-fixed to is:unresolved. It says nothing about auth requirements, pagination, rate limits, or response shape, which is a notable gap for a zero-annotation tool.

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 sentences, zero filler, with the identity and scope front-loaded before the implementation detail. Every sentence carries information an agent can use.

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 annotations and no output schema, the description should do more work than it does: it never characterizes the returned issue records (fields, ordering, whether stats/handlers are included) or pagination behavior. The endpoint detail partially compensates, and the fully documented schema covers inputs, but the behavioral picture is incomplete.

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 description coverage is 100%, so all four parameters (limit, environment, statsPeriod, sentry_project) are already documented in the schema with defaults and examples. The description's 'relative window' phrasing merely echoes statsPeriod without adding format or constraint detail, so the baseline 3 applies.

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+resource combination ('unresolved Sentry issues') with an explicit scope ('over a relative window'), which is unambiguous. It does not, however, differentiate itself from siblings such as whats_broken_since_last_deploy or incident_snapshot, which plausibly surface overlapping data, so the agent gets no direct comparison.

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?

Calling itself a 'low-level building block' implies the intended usage pattern (a primitive to compose into higher-level flows rather than a direct answer tool), which is reasonably strong implied guidance. But there is no explicit when-to-use/when-not-to-use statement and no named alternative, so the agent must infer that the composite siblings are preferred for direct questions.

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