get_space

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

No annotations are provided, so the description carries full burden. It states it retrieves details but doesn't disclose behavioral traits like whether it's a read-only operation, requires authentication, has rate limits, or what format/details are returned. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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, efficient sentence that front-loads the core purpose ('Get the current space details') and adds necessary context ('the one from STORYBLOK_SPACE_ID') without any wasted words. Every part 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?

Given 0 parameters and 100% schema coverage, the input side is well-covered. However, with no annotations and no output schema, the description doesn't explain what 'details' are returned or any behavioral constraints. For a simple retrieval tool, it's minimally adequate but leaves the agent guessing about the response format and operational context.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds value by specifying that it retrieves details for 'the one from STORYBLOK_SPACE_ID', clarifying that the space is determined by an environment variable rather than a parameter. This compensates adequately for the simple parameter case.

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 ('Get') and resource ('current space details'), specifying it retrieves the space identified by STORYBLOK_SPACE_ID. It distinguishes from siblings like 'update_space' (which modifies) and 'fetch_*' tools (which list multiple items), but doesn't explicitly contrast with other single-item retrieval tools like 'get_story' or 'get_asset'.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies it's for retrieving details of a specific space, but doesn't clarify if this is the only way to get space information or when to choose it over other tools like 'fetch_*' for listing spaces (though no such sibling exists in the list).

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