delete_dock

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Delete a dock' without mentioning side effects, permanence, authorization needs, or error conditions. The existence of a hardDelete parameter is not explained.

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 short (3 words), but this underspecifies the tool. Conciseness should not sacrifice necessary information. There is no structure or explanation, making it less helpful than a minimally adequate description.

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?

Given the tool's complexity (2 params, no output schema), the description is incomplete. It does not cover return value, failure modes, or relationship to sibling tools. The agent lacks context to use it correctly.

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% (both parameters have descriptions). Baseline is 3. The description adds no additional meaning beyond the schema, so no extra points. It does not clarify how parameters interact or special cases.

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 states the verb 'Delete' and the resource 'a dock', making the purpose clear. However, it does not distinguish from sibling delete tools (e.g., delete_appointment, delete_warehouse) which have identical phrasing. A 4 is given for clear purpose but lack of differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like delete_appointment or update_dock. There is no mention of prerequisites, context, or exclusion cases. This leaves the agent without sufficient direction.

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