get_issue_changes_summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context by stating the summary is 'compact' (implying it may not include every detail) and listing the specific change types included, but it does not disclose deeper behaviors like pagination or format constraints.

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?

The description is lean and well-structured: the purpose appears in the first sentence, and the argument list follows immediately. There is no redundant wording; every sentence adds information.

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 read-only tool with an output schema (not shown), the description covers the essential purpose and parameters. It is complete enough for an agent to invoke correctly; the only minor gap is the lack of explicit guidance on how this relates to similar change-related tools (e.g., get_issue_history).

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 carries full responsibility for parameter meaning. It does so exceptionally: issue_id is clarified as 'Issue ID or URL', since is explained as an 'ISO date filter' with an example, and instance is noted as optional. This goes far beyond the bare schema and fully compensates for the lack of property descriptions.

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 begins with a specific verb ('Get') and resource ('compact summary of issue changes'), then enumerates exactly what it covers: state transitions, comments, time logged. This clearly distinguishes it from siblings like get_issue (full issue data) or get_issue_history (raw history).

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 purpose: an agent can infer that this tool is for obtaining an overview of issue changes. However, there is no explicit guidance on when to prefer this over related tools such as get_issue_history or poll_changes, nor any mention of alternatives or exclusions.

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