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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination, filtering, result ordering, or what a 'template' contains. The operation ID is metadata, not behavioral context.

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 body is a verbatim duplicate of the same URL sentence, wasting half the text without adding information. It is short, but the space is spent on repetition and an opaque operation ID rather than a front-loaded statement of purpose.

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 2-parameter list endpoint with 0% schema description coverage and no output schema, the description should explain the query surface and the shape of the returned template list. It does neither, leaving the agent dependent on a separate describe_operation call before it can call this tool correctly.

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 parameters ('query' and 'params') are untyped free-form objects with no property descriptions. The one useful clue — that the native request schema must be obtained via describe_operation — is present but does not say what belongs in 'query' versus 'params' or give any filter examples.

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 repeats the REST path 'GET /api/lease-summary-templates' twice, which restates the title verbatim rather than explaining what the tool returns. An agent can infer it lists lease summary templates, but nothing distinguishes it from the sibling get_lease_summary_templates_by_id_31c0499dc0bb0d7124130cc8 beyond the raw URL.

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 many siblings (e.g. getting a single template by id, or the tenant-logo variant). The only routing hint is 'describe_operation provides native request schemas', which is a schema-lookup pointer, not usage guidance.

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