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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not state that the response is a PDF (binary/content-type), whether the PDF is generated on demand, or any latency/size considerations, which are the behaviors an agent actually needs here.

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 identical sentences back-to-back waste half the text, and the remaining line is an operation-ID/describe_operation pointer. Nothing is front-loaded beyond the endpoint string.

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 PDF-returning read endpoint with a nested params/query schema and no output schema, the description omits return type, parameter meaning, and any alternative-route guidance. It is not wrong, but it is far from sufficient to invoke confidently.

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 the description gives no parameter information at all — it does not explain that params.id is the lease identifier or that the free-form query object exists. With a nested-object schema and no coverage, the description should compensate but does not.

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 a literal restatement of the tool name/endpoint path, repeated twice. It does convey the resource (a lease's summary PDF keyed by id), but only because the endpoint path itself does, not because the description adds explanation of what the call returns or produces.

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?

No when-to-use guidance and no comparison to the many sibling lease tools (e.g., get_leases_by_id_0c975b3ee292145149f87dad, get_contracts_by_id_summary_pdf_83b2bd1d0bd828cd76581a65). The only actionable hint is 'describe_operation provides native request schemas', which is a pointer, not a usage rule.

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