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

Annotations already establish readOnly, idempotent and non-destructive behavior, so the bar is lower. The description nonetheless adds a genuine behavioral nuance beyond the annotations: this check does not reserve the deletion and results can be stale, since delete_agent performs an atomic re-check. It omits what the returned dependency data looks like, which matters given there is no output schema.

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?

Two short sentences, with the core action front-loaded and the non-reservation caveat immediately following. No filler and nothing that could be trimmed without losing meaning.

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 single-parameter read-only check with no output schema, the description covers the essential call-correctness concerns: purpose and the non-atomic/racy nature of the result. The main gap is that it does not indicate the shape or meaning of the returned dependencies (e.g. whether it lists agents, campaigns, or contacts), which an agent would need to interpret the result.

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?

There is one required parameter, agent_id, with 0% schema description coverage, so the schema adds no meaning. The description never mentions the parameter; it is only inferable from the tool's subject matter. Adequate but no added semantic value.

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?

States a specific verb and resource ('Read the current dependencies preventing deletion'), which an agent can immediately map to a pre-deletion inspection step. It explicitly names the sibling it complements (delete_agent), making the distinction between the two operations unambiguous.

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 defines the usage context clearly: run this to see what blocks deletion, and note that it is non-binding because delete_agent re-checks atomically. It does not spell out an explicit 'when not to call this' case (e.g. that calling it is optional since delete_agent performs its own check), so it stops just short of full routing guidance.

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