get_space

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only "detailed metadata" and says nothing about pagination/cursor continuation behavior, which for this tool is the non-obvious trait. With annotations carrying the burden, this is an acceptable but thin 3.

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?

Two short sentences with zero filler, the core purpose front-loaded and the sibling routing appended. Every clause 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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. For a 4-parameter read tool with nested offset objects, the description is adequate, with only the missing detail enum explanation and cursor/pagination note as residual 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?

Schema description coverage is 50%: text_offsets and section_offsets are self-documented in the schema, while space_id and the summary/full detail enum are not. The phrase "detailed space metadata" faintly gestures at the detail level but never explains summary vs full, so the description does not close the gap.

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?

States a specific verb+resource ("Read detailed space metadata") and explicitly rules out what it does not return by pointing to list_boards and list_space_cards. It does not, however, distinguish itself from the closest sibling list_spaces, so an agent must infer when to fetch one space versus enumerate all of them.

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?

Gives explicit routing for adjacent data (boards to list_boards, cards to list_space_cards), which is genuine when-to-use guidance. There is no exclusion or precondition for get_space itself, and the list_spaces alternative is unaddressed.

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