iterate

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

Reveals key behavioral trait (non-blocking, polling required) which is critical. No annotations present, so description carries burden. However, does not disclose side effects, authorization, rate limits, or idempotency. Adequate but not rich.

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 well-structured sentences. First sentence states purpose, second provides post-invocation guidance. No superfluous words. Highly efficient.

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 purpose and follow-up actions, but lacks detail on what 'iterate' entails (e.g., does it modify a design? Create a session?). No return value description. Acceptable for a simple tool but could be more complete given sibling ambiguities.

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 0%, and description does not explain the parameters (projectId, prompt) at all. The description should add meaning beyond schema, but it provides no parameter information. This is a significant 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?

The description clearly states the action: 'Send a chat message to iterate on the design.' It uses specific verb+resource, distinguishing it from general chat tools like 'send_message' and generation tools like 'generate'.

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?

Explicitly describes the asynchronous nature: non-blocking, returns quickly, then need to poll or watch status. Provides clear next steps. Lacks explicit when-not-to-use or comparison with siblings, but context is sufficient.

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