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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that - no mention of what the endpoint returns (a binary image? a URL?), authentication needs, or content type, which matters for a logo retrieval endpoint.

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 single sentence is duplicated verbatim, which is pure waste, and the remaining sentence is a generic boilerplate pointer to describe_operation. No front-loaded purpose statement.

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, a nested free-form object parameter with no documentation, and no description of the endpoint's response or behavior. For a tool whose input contract is essentially opaque, the description provides almost nothing an agent needs to invoke it 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% for the two parameters: 'query' is a free-form object with additionalProperties and 'params' is an empty object. The description does not compensate at all - it only says describe_operation has native schemas, leaving an agent no way to know what query keys are valid without another call.

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 verbatim restatement of the tool name/title ('GET /api/lease-summary-templates/tenant-logo'), repeated twice. It does imply fetching a tenant logo for lease summary templates, but that is inferred from the URL path rather than explained, and there is no differentiation from the many sibling lease-summary-template tools.

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 guidance on when to use this tool versus alternatives like get_lease_summary_templates_by_id or the general execute_read. The only hint is a pointer to describe_operation for request schemas, which is a fallback mechanism rather than usage guidance.

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