Get Space

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'gets details,' which implies a read operation, but does not explicitly state that it is non-mutating, whether it requires specific permissions, or what happens if the space_id is invalid. No error behavior or return format is disclosed beyond the schema.

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 concise sentence with no wasted words. It is appropriately brief for a simple getter tool. However, it is so minimal that it borders on under-specification, lacking any additional context that could be included without becoming verbose.

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 tool with one parameter and an output schema present, the description is minimally adequate. It communicates the core function, and the output schema covers return values. However, the absence of any usage guidance or behavioral transparency makes it less complete than it could be, especially given the existence of sibling tools.

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 provides 100% coverage, describing space_id as 'UUID of the space.' The description adds no additional meaning about the parameter—it only implies the space is identified by ID. Since the schema already documents the parameter adequately, a baseline score of 3 is appropriate; the description does not enhance it.

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 'Gets the details of a space,' which clearly identifies the verb (gets) and resource (space). It implies a single-space retrieval by ID, but does not explicitly contrast with list_spaces, which lists multiple spaces. The purpose is understandable but could benefit from naming the sibling to disambiguate.

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 is provided on when to use this tool versus alternatives. There is no mention of when to prefer get_space over list_spaces or get_page, and no exclusions or prerequisites are stated. The description relies entirely on the agent's inference.

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