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

Annotations already provide readOnlyHint=true and destructiveHint=false, and the description adds valuable credential handling context: 'BYOK — credentials transit in-memory only, never stored.' This goes beyond the annotations and informs the agent about security behavior. No contradiction with 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 two well-structured sentences. The first defines purpose, the second provides usage examples and a security note. There is no wasted text.

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 rich schema (all 6 parameters documented), output schema, and annotations, the description covers the essential context: purpose, usage scenarios, and credential handling. It doesn't mention pagination or error behavior, but that is not critical given the schema defaults. No major gaps.

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 100%, so the baseline is 3. The description mentions 'label/assignee/component' which relates to JQL usage, but does not add specific parameter semantics beyond what the schema already documents. The schema carries the full burden for parameters.

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 'Search Jira using JQL (Jira Query Language)' and what it returns: 'matching issues with key fields.' This specific verb+resource+scope distinguishes it from siblings like fetch_jira_issue (which likely fetches a single issue) and post_jira_comment.

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?

Provides clear when-to-use context: 'Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component.' It gives scenarios but does not explicitly mention when not to use or name alternatives, so it's a 4 rather than a 5.

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