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

Annotations already declare read-only and idempotent, but the description adds useful detail: long-poll up to 25s, in-progress returns poll_after_seconds, and terminal state leads to creations_show. No contradiction with annotations.

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 concise sentences that deliver the essential information without redundancy. Each sentence adds value.

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?

Covers polling behavior, timeout limit, and terminal next-step, which is sufficient for this polling tool. Lacks details about response fields, but no output schema is provided, so this is acceptable.

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 description explains timeoutSeconds (long-polls up to 25s) and implies workflowRunIdentifier by context, compensating for the lack of schema descriptions. It doesn't explicitly define workflowRunIdentifier, but its name is self-explanatory.

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 polls spaces_run status, and the context about timeout and terminal behavior makes its purpose unambiguous.

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 explains when to use (poll a spaces_run) and what to do on terminal state (call creations_show), but doesn't explicitly distinguish from alternatives like magnific_spaces_edit_status or magnific_creations_wait.

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