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

The description says the tool supports 'authorized editing of the lease identifier,' which implies a mutation capability, while the annotations declare readOnlyHint=true. This is a direct contradiction about whether the tool writes data, so behavioral transparency is critically impaired.

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 description is short and front-loads the main purpose in the first sentence. The remaining sentences are compact, though the 'authorized editing' statement introduces confusion rather than useful clarity.

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 simple one-parameter read tool, the description covers the basic purpose but leaves key gaps: it does not clarify the lone parameter, does not explain the return shape, and contains an editing claim that conflicts with read-only annotations. Those omissions and the contradiction make it incomplete for reliable invocation.

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 only one parameter, leaseId, and schema description coverage is 0%, so the description must compensate. It mentions 'lease identifier' only in the context of editing, but does not explain the parameter's role, expected format, or required nature.

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 gives a specific verb and resource: reviewing an existing lease and its saved terms. It is clearer than a tautology, but it does not distinguish this tool from the many sibling lease-detail endpoints, which makes it only partially differentiated.

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 implies a use case by saying it supports drill-down from dashboards, and it sets a boundary by saying it never infers accounting or payment evidence. However, it names no alternatives and gives no explicit when-to-use or when-not-to-use guidance versus the numerous lease-related sibling tools.

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