survey_agent_delete

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

With no annotations provided, the description must disclose behavioral traits. It clearly states the tool is destructive (permanently delete) and requires a confirmation flag, giving the agent essential safety information. This is adequate for a deletion tool.

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 concise and front-loaded, consisting of two short sentences with zero waste. Every word 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?

Despite 2 parameters, no enums, and presence of an output schema, the description covers the core destructive nature and safety requirement. For a simple deletion tool with an output schema, this is sufficiently 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 description coverage is 0%, so the description must compensate. It mentions survey_id implicitly by stating 'survey' but does not explain the format or meaning of the parameters beyond the schema. The confirm parameter is briefly noted. Baseline 3 is appropriate as it adds minimal meaning beyond schema.

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 (permanently delete) and the resource (survey, DSL file, and answers). It distinguishes from siblings like survey_agent_update, survey_agent_archive, and survey_agent_get, though it could be more explicit about which sibling tools are similar.

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?

The description mentions the need for confirm=true, implying a safety guard, but does not say when to use this tool vs alternatives (e.g., survey_agent_archive for soft deletion). No explicit when-not-to-use or prerequisites beyond confirmation.

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