Get Multiple Issues

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

Adds significant information beyond annotations: max 5 concurrent requests, null return for missing/inaccessible IDs, and response counters ('requested', 'found', 'failed'). No contradiction with readOnlyHint=true.

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?

Three concise sentences, front-loaded with purpose. 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?

Fully explains the batch retrieval behavior, parallelism limits, error handling, and response summary counters. Complete for a read-only batch tool with annotations already covering safety.

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 already covers ids parameter with comprehensive description. Description adds crucial behavioral detail: null returned per ID on 404/403/error instead of failing the whole call, enhancing schema meaning.

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?

Clearly states 'Retrieve multiple MantisBT issues by their numeric IDs' with specific verb and resource. Distinguishes from sibling tools get_issue (single) and list_issues (unfiltered).

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?

Describes parallel execution and error handling behavior (null for missing IDs, never fails). Provides context for use but does not explicitly contrast with alternatives like get_issue or list_issues.

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