get_space_info

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get', implying a read operation, but does not elaborate on whether any side effects exist, required permissions, error behavior, or what 'structures and collections' entail. This is insufficient for a tool with no annotation support.

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, clean sentence that is front-loaded with the key action. It avoids unnecessary words and is easy to parse. While more detail could be added, the conciseness is appropriate for the limited content it provides.

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 the tool's simplicity (one parameter, no output schema, no annotations), the description gives a basic idea that the tool returns structures and collections. However, it lacks details on the exact return format, any pagination, error conditions, or what 'structures' and 'collections' mean in this context. It is barely adequate for a minimal understanding.

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 schema has zero description coverage, and the description does not compensate by explaining the spaceid parameter. It only says 'of a space', which weakly hints at the need for a space identifier but does not clarify the parameter format, nesting, or purpose. The parameter name 'spaceid' partially helps, but the description adds minimal value beyond the schema.

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 'Get structures and collections of a space' clearly states a specific verb (Get) and resource (structures and collections of a space), making it evident what the tool does. It does not explicitly differentiate from sibling tools like get_spaces, but the phrase 'of a space' implies it targets a single space's details rather than listing spaces.

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?

There is no guidance on when to use this tool versus alternatives such as get_spaces or search_content. The description does not state any prerequisites, exclusions, or context in which this tool should be preferred, leaving the agent without explicit selection criteria.

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