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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no note on what 'current' means (latest vs. effective-as-of-date), whether an empty result is possible when no assessment exists, or how the record is versioned.

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?

It is short, but the single substantive sentence is duplicated word-for-word, so half the content is pure waste. The operation ID and the describe_operation pointer are tacked on without being framed in a way that helps selection.

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 tool with no output schema, a nested 'query' object, and 0% parameter documentation, the description should explain what is returned and how to scope the call. It explains neither, leaving the agent unable to predict the response shape or the meaning of the path parameter.

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 carries the full burden of explaining leaseId and the free-form 'query' object. It provides nothing — no format, no source of the ID, no explanation of what query parameters are accepted. The only implicit signal is that leaseId sits in the path.

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 text is a raw endpoint path repeated verbatim, restating the tool name/title with no plain-language statement of what a 'classification assessment (current)' actually is. An agent can infer it fetches the current lease classification assessment for a lease ID, but there is no differentiation from the near-identical sibling get_accounting_leases_by_id_classificat_ebade756392ea13ae975fd9a.

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, when-not-to-use, or prerequisite information is given. The only routing hint is 'describe_operation provides native request schemas', which tells the agent how to get a schema, not when this tool is the right choice over the many sibling lease-classification tools.

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