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

Goes well past the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true) by disclosing that the public path returns a pending request rather than a Space, that sign-in or a linked agent is required, and that both paths are retry-safe when the same idempotency_key and arguments are reused. Those are exactly the behaviors an agent cannot infer from structured fields.

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?

Four dense sentences with the default behavior front-loaded, followed by the exception, the retry contract, and the auth requirement. No filler, and the ordering matches how an agent decides how to call it.

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, yet the description still flags the non-obvious return semantic (pending request, not a Space) that the schema alone would not convey. With auth, idempotency, and both modes covered, an agent has everything needed to call it correctly on the first try.

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%, so baseline is 3; the description adds narrative value by tying public=true to the purpose requirement and the 80-character title cap, and by spelling out the idempotency contract (same key + same args on retry). It mostly restates schema text, which keeps it below a 5.

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?

Specific verb+resource ('Create a Space') with both operating modes named and contrasted: an immediate private Space vs. a moderated Community Space request. It also names the sibling (space_get_request) that continues the workflow, so an agent can place the tool in the lifecycle without opening any schema.

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?

It states the default path (private, you as owner) and the condition that switches behavior (public: true, which requires purpose), plus where to read the outcome. It stops short of naming alternatives or when not to use it — e.g. it never mentions space_ensure_personal for the personal-space case — so routing is clear but not exhaustive.

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