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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention whether deletion is permanent, whether confirmation is required, any side effects, idempotency, or authorization needs. The description only points to an endpoint without explaining what happens when the tool is invoked.

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 sentence with no wasted words, so it is concise. However, the brevity sacrifices substance; it provides barely more than the tool name and endpoint. A concise but insufficient description is not ideal.

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?

The tool lacks an output schema and annotations, so the description must provide context about return values, success/failure behavior, and operational semantics. It does not. The description simply states the endpoint and parameterized context is absent, leaving the agent without enough information to safely and correctly use the tool.

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 100%, so all parameters have descriptions in the schema. The tool description adds no additional meaning beyond the schema, which is sufficient to meet the baseline. However, some parameter descriptions (e.g., body) are vague, but this is not the description's fault.

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 references the Lever DELETE endpoint and resource, but it reads more as a command to use the API than a functional statement of what the tool does. It distinguishes the resource (feedback templates) but does not clearly say 'deletes a feedback template' or describe the outcome. The verb is implied by the HTTP method, not explicitly stated.

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 gives no guidance on when to use this tool versus alternatives (e.g., create_feedback_template, update_feedback_template) and no exclusions or prerequisites. The phrase 'for recruiting operations' is too generic to help an agent decide between deletion and other operations.

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