Get multiple issues

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

Discloses concurrency limit, null-for-missing behavior, and counters, adding significant value beyond annotations (readOnly, idempotent, not destructive). No contradictions.

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?

Two concise sentences, no fluff. Front-loaded with purpose, conveys all necessary information efficiently.

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?

Covers key behaviors (concurrency, null handling, counters) for a read-only batch fetch. No output schema, but counters suffice. Could specify return format, but not critical.

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 covers parameter 'ids' with description. Tool description adds concurrency limit and error handling details, enhancing meaning beyond schema. Baseline 3 raised due to additional context.

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 'Fetch several issues by id in one call', using specific verb and resource. Distinguishes from sibling 'mantis_get_issue' by indicating batch operation.

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?

Indicates max 5 concurrent calls and tolerant behavior for missing IDs, guiding when to use this batch fetch. Could explicitly contrast with search or single get, but context is clear.

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