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

With no annotations, the description carries the behavioral burden. It discloses the return shape (Markdown brief, raw fields, screenshot image) and implies a read operation by omission of mutation, but it does not state that the call is non-mutating, whether the id must exist, error behavior for a missing id, or whether the screenshot is a link or inline image.

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 sentence that front-loads the purpose and lists the returned components in a parenthetical. It is compact, though the parenthetical is dense and could be slightly tightened.

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 2-param read tool with no annotations and no output schema, the description adequately covers what is returned but leaves behavioral gaps (read-only nature, missing-id errors) and does not clarify the screenshot parameter's effect beyond implying an image is returned.

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 100% and both parameters have schema descriptions, so baseline is 3. The description adds the meaning of screenshot output (as an image) but does not add syntax or format detail beyond the 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?

States a specific verb and resource ('get issue', 'one report in full') and enumerates the returned fields, which is clearer than the sibling list_issues. It doesn't explicitly contrast with list_issues, but the singular 'one report' implied by the id parameter constrains to a single retrieval.

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 strongly implied by the required id parameter and the singular framing versus list_issues, but there is no explicit when-to-use or when-not statement. No prerequisites or claim that the issue must already exist are given.

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