get_vibe_edit_status

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

With no annotations, the description fully carries behavioral disclosure. It reveals the tool is non-mutating, that medium truncates before/after to 200 chars, full returns untruncated data, error is populated on failure, and instructs the agent to surface the error. No contradictions with annotations (none present).

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 dense but every sentence earns its place. It front-loads the core purpose, then systematically covers detail modes, error handling, and next-step behavior. Nothing is redundant or filler.

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?

No output schema exists, so the description compensates by fully describing the return structure for each detail level, including the error field. It also connects to sibling tools and provides operational sequence (poll → apply). Given the tool's complexity and missing annotations, this description is complete.

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 significant meaning beyond schema: it explains that operationId comes from vibe_edit_landing_page, specifies what each detail level returns, and notes that index/path from the medium response should be used in apply_vibe_edit. This goes beyond the schema's generic parameter descriptions.

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 opens with 'Poll vibe (AI) edit session status' — a specific verb ('poll'), resource ('vibe edit session status'), and clear scope. It distinguishes from siblings by explicitly stating 'this tool never applies anything' and referencing apply_vibe_edit as the follow-up.

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?

Provides explicit guidance: when status is 'completed', call apply_vibe_edit next. Also explains when to use each detail level ('medium' is the REVIEW view, 'short' is cheap, 'full' is raw), and how to use resulting values to select a subset in apply_vibe_edit.

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