todo_multi_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates that this is a read-only batch fetch operation, which is important, but it does not describe failure behavior, return format, or what happens if some URLs are invalid or missing. This is adequate but not rich.

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 sentences with no wasted words. The core action is front-loaded, and the efficiency note is directly relevant to tool selection. Every sentence earns its place.

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 simple one-parameter read-only batch fetch tool, the description covers the essential invocation context: what to pass, why to use it, and when it is appropriate. It lacks detail about error handling or response shape, but the tool's simplicity and clear purpose make this a minor gap.

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 coverage is already 100%, so the baseline is 3, but the description adds meaning beyond the schema by emphasizing that the todo_urls must be 'exact' URLs and that the tool fetches 'specific' todos in batch. This clarifies that the parameter is not a search query and that multiple exact URLs are expected.

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 ('fetch'), a resource ('todos'), and a precise mechanism ('by their URLs'). It also distinguishes the tool from list/query alternatives by emphasizing 'specific todos' and batch retrieval, so an agent can clearly understand its purpose.

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 gives a clear usage condition: use this when you have 'exact todo URLs' and want to batch-fetch multiple todos. It also notes that this is 'more efficient than fetching one by one,' which provides practical guidance, though it does not explicitly name the alternative tool to use when URLs are unavailable.

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