confluence_get_space

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('Get details'), but does not disclose specifics such as authentication requirements, rate limits, or what 'details' encompass. Basic transparency is present but lacks depth.

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 one sentence with no wasted words. It is efficient, though it could incorporate additional context (like return details) 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?

The description explains how to call the tool but does not describe the output structure (no output schema). For a retrieval tool, the agent might benefit from knowing typical fields returned (name, key, etc.). Adequate for a simple tool, but leaves gaps.

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 parameter space_id is fully documented in the schema (100% coverage). The description repeats its purpose ('by its ID') without adding new meaning. Given high schema coverage, 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 action ('Get details') and the resource ('a Confluence space by its ID'). It effectively distinguishes from sibling tools like confluence_get_space_by_key and confluence_list_spaces, which operate on different identifiers or return lists.

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 when you have a space ID, but provides no explicit guidance on when to use this tool over alternatives (e.g., by key or list). No when-not-to-use 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.