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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds nothing about what a termination record contains, whether 404s are expected, or any access constraints — it only repeats the endpoint and points at describe_operation.

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 same sentence is emitted twice back-to-back, which is pure waste, and the operation ID hash is noise for an agent. There is no front-loaded statement of intent beyond the path itself.

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?

This is a nested-object, 0%-documented-parameter tool with no output schema, so the description needed to explain the parameter shape and response nature. It does neither, leaving only a pointer to describe_operation as a fallback.

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%, so the description is the only place parameter meaning could be supplied, and it delivers none. The path template hints at a terminationId, but the schema already marks it required with a length constraint, and the free-form 'query' object is entirely unexplained.

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 is the raw HTTP path duplicated verbatim, which is essentially a restatement of the name and title. It does convey that a single termination is fetched by ID, but adds no differentiation from siblings like get_terminations_pending or get_terminations_lease_by_leaseId.

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?

There is no statement of when to use this tool versus the other termination endpoints or list operations. The only routing hint is that describe_operation holds native request schemas, which is about schema discovery rather than tool selection.

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