Get Issues Development Info

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

With readOnlyHint=true, the safety profile is already covered. The description adds that it batch retrieves PRs, commits, and branches, disclosing the data scope. It does not mention pagination, rate limits, or performance implications, but the annotation lowers the bar for behavioral disclosure.

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 focused sentences, front-loaded with the purpose and clarifying the batch behavior. No filler or 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?

For a read-only batch retrieval tool with a full input schema and an output schema, the description sufficiently covers the purpose, scope, and data categories. No critical information is missing for an agent to select and invoke it.

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?

All three parameters have full descriptions in the schema (100% coverage). The description's mention of PRs, commits, branches aligns with the data_type parameter but adds no new detail beyond what the schema already provides, so it meets the baseline without extra compensation.

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 states a specific verb ('Get') and resource ('development information') and clarifies batch scope for 'multiple Jira issues'. It distinguishes from the singular sibling tool jira_get_issue_development_info by emphasizing 'multiple issues'.

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 clearly implies a batch use case: 'for multiple issues at once' suggests it is intended for bulk operations, contrasting with the singular alternative. However, it does not explicitly name that alternative or provide when-not guidance, stopping short of a 5.

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