retrieve_single_datasource

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'retrieves', which implies read-only, but lacks details on permissions, error handling, or response format. For a simple read tool, this is minimal transparency.

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 with no filler or redundant information. It is front-loaded with the action and resource, and every word is necessary.

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?

The tool is simple: one required parameter and no output schema. The description is adequate but leaves gaps: it mentions 'from a specified Storyblok space' but the space is not a parameter (likely inferred from authentication), and it does not describe the return value. Overall, it is minimally complete for a straightforward retrieval.

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 has 100% description coverage for the only parameter 'datasource_id' (described as 'ID of the datasource to retrieve'). The tool description adds no additional parameter information, so baseline score of 3 is appropriate.

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 verb 'retrieves' and the resource 'single datasource' from a specific context ('specified Storyblok space'). It distinguishes itself from sibling tools like 'retrieve_multiple_datasources' (which lists multiple) and CRUD tools like 'create_datasource', 'update_datasource', and 'delete_datasource'.

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 implies usage for retrieving one datasource by ID, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'retrieve_multiple_datasources' for listing all datasources). No exclusions or prerequisites are mentioned.

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