retrieve_multiple_datasource_entries

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

With no annotations, the description carries full burden for behavioral traits. It only states it retrieves entries, implying a read operation, but omits details like pagination, rate limits, response format, or side effects. The agent has insufficient insight into what happens beyond the basic action.

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 efficient sentences that front-load the purpose and essential constraint. No wasted words, easy to parse.

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 and moderate complexity (3 params, 0 required in schema), the description covers the core action but lacks information on return format, pagination, or error conditions. Adequate but not fully complete for effective tool invocation.

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?

Input schema has 100% coverage, baseline 3. The description adds the constraint that datasource_id or datasource_slug is required (though schema marks both optional), providing meaningful guidance beyond the structured schema. This elevates the score above baseline.

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?

Description clearly states the tool retrieves multiple datasource entries from a Storyblok space, using specific verbs and resource. It distinguishes itself from sibling tools like retrieve_single_datasource_entry and retrieve_multiple_datasources by specifying 'multiple entries' and requiring datasource_id or slug.

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?

Description mentions one of datasource_id or slug is required, providing basic usage context. However, it does not explicitly compare with alternatives (e.g., when to use multiple vs single) or state prerequisites like authentication or space permissions.

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