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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond the path: no indication of what the template contains, whether it is static across modules, or whether it requires any setup such as an existing lease batch.

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?

Short, but the first sentence is duplicated verbatim, which is pure waste, and the remaining content is the operation ID plus a pointer to another tool. Front-loading is irrelevant when there is nothing substantive to front-load.

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, 0% parameter coverage, and a nested-object schema, yet the description says nothing about the response (file bytes vs JSON template definition) or the accepted query parameters. An agent could not call this confidently without first calling describe_operation.

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% with two free-form objects (a generic 'query' with additionalProperties and an empty 'params'), so the schema tells an agent almost nothing. The description does not compensate at all — it only defers to describe_operation without explaining what the query object is for or what keys are valid.

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 restates the HTTP route 'GET /api/rent-import/template' twice, without saying what a rent import template is, what format it is returned in, or how it differs from siblings like get_rent_adjustment_import_template or get_import_template_by_module. The name and route carry all the meaning.

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 statement of when to call this versus the other import-template and import-workbook tools in the sibling list. The only pointer is that describe_operation exposes native request schemas, which is a schema-lookup hint rather than a usage condition.

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