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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so safety is covered elsewhere. The description adds zero behavioral context beyond the path — no note on draft lifecycle/state, permissions, or what happens to non-existent drafts. It does not contradict annotations.

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 endpoint sentence is duplicated verbatim, wasting half the text, and the remaining content is a machine ID plus an indirection to another tool. Brevity is achieved through under-specification rather than density.

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?

No output schema exists, so the description should explain what a draft fetch returns, yet it says nothing about the draft object or its relationship to lease amendments. With 0% param coverage and nested input objects, the definition is not sufficient to call the tool confidently without a second lookup.

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 path params (leaseId, draftId) are undocumented in the schema. The description does not compensate at all — the path template merely echoes the parameter names with no format, constraint, or sourcing guidance.

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 only restates the tool name/path twice ('GET /api/leases/:leaseId/amendment/manual/drafts/:draftId') plus an opaque operation ID. It conveys no plain-language statement of what a 'manual amendment draft' is or what retrieving it accomplishes, so the agent learns nothing beyond what the title already shows.

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 when-to-use guidance, no distinction from the other amendment/manual siblings (a33db819..., a885bf41...), and no prerequisites. The only pointer is the generic 'describe_operation provides native request schemas', which is a schema-lookup instruction, not usage guidance.

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