retrieve_multiple_tasks

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

With no annotations, the description is the sole source of behavioral info. It only states the action, with no details on side effects, authentication needs, rate limits, error handling, or pagination behavior. This is insufficient for an agent to understand the tool's behavior.

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 a single sentence of 12 words, concise and front-loaded. It efficiently conveys the tool's purpose without unnecessary details, though it could be slightly more precise by omitting 'using the Management API'.

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 no output schema, the description should at least indicate the return format (e.g., list of tasks with pagination info). It lacks information on ordering, filtering, and handling of empty results, making it incomplete for a paginated list tool.

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?

The input schema already describes all three parameters (space_id, page, per_page) with clear descriptions. The description adds no additional meaning or context beyond the schema, so it scores a baseline 3 for not adding value.

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 action (retrieve) and resource (multiple tasks) from a specific Storyblok space using the Management API. It distinguishes from sibling tools like retrieve_single_task, but does not differentiate among other retrieve_multiple_* tools for different resource types.

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?

No guidance on when to use this tool versus alternatives, such as retrieve_single_task or retrieve_all_extensions. No mention of pagination limits, filtering, or ordering. The description only implies usage for retrieving multiple tasks, without context on when it is appropriate.

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