passgage_delete_entrance

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

The description only repeats the verb 'Delete' which is already in the tool name. With no annotations provided, the description carries the full burden of disclosing behavioral traits like permanence, permissions, or side effects, but it fails to provide any additional context. This leaves the agent unaware of the destructive consequences.

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 a single concise sentence, front-loaded with the verb 'Delete' and the target resource. It contains no unnecessary words and is easy to parse.

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?

For a simple one-parameter delete tool, the description provides the essential action and target, but it lacks critical context such as irreversibility or side effects. Without annotations, this leaves a moderate gap in understanding, making it minimally viable but not thorough.

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 input schema already fully describes the single 'id' parameter as 'The UUID of the entrance to delete', covering 100% of parameter semantics. The description aligns by saying 'by ID' but adds no new meaning beyond the 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 uses the specific verb 'Delete' with the resource 'entrance' and method 'by ID', clearly distinguishing it from sibling tools like get_entrance, create_entrance, update_entrance, and track_entrance. Despite a minor grammatical error ('a entrance'), it unambiguously states the tool's function.

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 such as update_entrance or soft-delete options. The description simply states the action without any context, not mentioning that deletion is likely irreversible or that it should be used only when an entrance is permanently no longer needed.

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