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

With no annotations, the description carries the full behavioral burden, and it discloses the single most important trait: the tool fails with 501 and has no side effects. It adds no detail about what enrollment would do if re-enabled or what the error payload looks like, which keeps it short of a 5.

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?

'CURRENTLY DISABLED' is front-loaded where it will be seen first, and the alternative follows immediately. The trailing '### Responses: 200 Successful Response' block is leftover boilerplate that is arguably misleading given the 501 behavior.

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 disabled tool with two opaque params and no output schema, the description supplies everything an agent actually needs: do not call it, use create_sequence, schedule manually. Parameter documentation would be nice but is low-value while the endpoint is inert.

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 0% and both required parameters (prospect_handle, sequence_handle) are undocumented in the schema, yet the description says nothing about their format or where the handles come from. Since the tool is unusable this matters less, but the gap is real.

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 verb+resource ('Enroll Prospect') is clear, and the description immediately qualifies it with 'CURRENTLY DISABLED ... enrolls nobody', so an agent knows exactly what the tool would do and that it currently does nothing. It doesn't explicitly state what enrollment means (prospect into sequence), but the parameter names and sibling set make that inferable.

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?

Explicit when-not ('This tool returns 501 and enrolls nobody') plus a named alternative ('See create_sequence') and a concrete fallback ('Schedule follow-ups explicitly instead'). This is the strongest possible routing guidance for a dead tool.

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