get_flutter_stripe_issue

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

Annotations already indicate readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral details: returns a 'note' if the comment thread was too long, and returns an error object with a 'kind' field on failure. This goes beyond the structured annotations.

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 well-structured with a clear summary, usage guidance, parameter description, and return format. It is concise, front-loaded, and every sentence adds value without redundancy.

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?

Given the tool's simplicity (1 parameter, output schema provided), the description covers all necessary aspects: input, output, error handling, and usage context. No missing information for effective agent decision-making.

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 0%, but the description adds crucial meaning: 'issue_number: The GitHub issue number (e.g. 1234), not a URL.' This clarifies the format and avoids confusion. For a single parameter, this is effective.

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?

Description clearly states 'Fetch the full body and comments of one flutter_stripe GitHub issue.' This is a specific verb+resource pair, and it distinguishes from its sibling search_flutter_stripe_issues by focusing on retrieving full details of a single 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?

Explicitly tells when to use this tool: 'after search_flutter_stripe_issues has identified a candidate issue number.' It also explains why: 'to read the complete discussion — maintainer replies and community comments often contain the actual fix, workaround, or root cause.' This provides clear context and an alternative tool.

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