select_space

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

No annotations are given, so the description must disclose behavior. It only says 'select', implying a side effect (e.g., setting active space), but provides no details on permissions, reversibility, or state changes.

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 extremely short (6 words), but lacks necessary information. Conciseness without substance is insufficient.

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 (single param, no output schema, no annotations), the description should explain what 'selecting' entails, but it fails to do so, leaving critical 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 input schema has one parameter (spaceId) with 0% description coverage, and the description adds no meaning about the parameter's purpose or format.

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 'Select a space to work with' clearly indicates a verb ('Select') and a resource ('a space'). It implies setting a working context, which is distinct from listing or getting info, but does not explicitly differentiate from siblings like 'list_spaces' or 'space_info'.

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 such as list_spaces or space_info. The description lacks context for decision-making.

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