search_flutter_stripe_issues

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

The description discloses key behaviors beyond annotations: automatic retry with broadened search on no exact match, marking results with 'broadened_search', and return format with error handling. This adds value beyond the readOnlyHint, openWorldHint, and idempotentHint 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 clear paragraphs for purpose, usage, behavior, and parameters. It is concise without redundancy, front-loading the main goal and effectively using space for each aspect.

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 has 3 parameters (all fully explained), an output schema described in the return format, and error handling notes, the description is complete. It provides all necessary context for correct invocation and interpretation of results.

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?

With 0% schema description coverage, the description fully explains all three parameters: query (free-text, example given), state (enum with default), and limit (range and default). It also notes the output includes error on failure, compensating for missing schema 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 clearly states the tool searches GitHub issues in a specific repository (flutter-stripe/flutter_stripe) and distinguishes it from the sibling tool get_flutter_stripe_issue by mentioning that it returns excerpts for relevance judgment and advises using the sibling for full details.

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?

The description explicitly tells when to use (to check if a problem is already reported) and provides context such as automated broadened search on no exact match. It also mentions the alternative tool for full discussion, giving clear usage guidance.

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