issue_search

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

Since no annotations are provided, the description offers minimal behavioral context. It only discusses input modalities and does not mention limitations, rate limits, or specific error handling behavior.

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 highly concise, delivering all necessary core information in a single, direct sentence without any filler.

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?

The tool explains what it searches and how it searches. However, as a search endpoint, it lacks completeness regarding result structure, pagination behavior, or potential result volume limitations beyond the basic schema coverage.

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?

The description significantly aids the agent by explaining how the ambiguous 'query' parameter should be formatted. This semantic guidance is highly valuable, especially since the schema provides no description for this specific required input.

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 identifies the tool's action (Search), the resource (issues), and the method (JQL or plain text). This specificity is highly effective for an agent.

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?

It provides clear guidance on the input format by distinguishing between JQL and plain text search terms. While it doesn't explicitly name sibling tools to avoid (like issue_get), the action-verb distinction makes its purpose clear.

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