tp_delete_availability

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

With no annotations available, the description fails to disclose behavioral traits such as irrevocability, permission requirements, or side effects. It only states the action without warning of 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?

A single sentence, front-loaded with the key action. No extraneous information, but slightly under-specified for a tool with two parameters.

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 deletion tool with no output schema or annotations, the description provides minimal functional context. It is adequate but not robust enough to fully inform an agent about prerequisites or return values.

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 50%, but the tool's description adds no additional meaning beyond the schema. The 'athlete' parameter is described in the schema, while 'availability_id' lacks any description. The description does not compensate for the missing coverage.

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 'Remove an availability entry' clearly states the verb (Remove) and resource (availability entry), making it distinct from sibling tools like tp_create_availability or tp_get_availability. However, it lacks additional scope details that would separate it further.

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, when not to, or how it compares to alternatives. The description is a bare statement without any contextual direction.

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