confluence_get_space

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

The description discloses key behaviors: trimming of output by default, the resolution of spaceKey to numeric ID, and the full parameter to bypass trimming. With no annotations, this provides useful context. Missing explicit read-only hint, but the verb 'get' implies a safe read operation.

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 two sentences with front-loaded purpose and concise details. Every sentence adds value without redundancy.

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 (7 params, none required, no output schema), the description adequately covers identification, trimming, and resolution. The sibling tools do not require additional context for differentiation.

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?

Schema coverage is 100% with descriptions. The description adds significant meaning beyond the schema: explains that spaceId or spaceKey are alternatives, describes resolution behavior for spaceKey, and clarifies trimming behavior with full parameter. This fully compensates for any schema gaps.

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 tool 'gets a specific space by ID or key' and distinguishes it from sibling tools like get_spaces (list) and get_pages_in_space. The mention of two identifier methods adds specificity.

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 explicitly says to provide either spaceId or spaceKey, and the purpose of getting a specific space is clear. However, it does not explicitly mention when not to use this tool (e.g., when needing to list spaces) or direct to alternative tools.

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