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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds nothing beyond that. It does not disclose what form the template takes (downloadable file, content type, whether it is empty scaffolding) or any auth/format constraints.

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 informational sentence is duplicated word-for-word, wasting the front-loaded position. Structure is essentially boilerplate rather than purposeful content.

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?

With no output schema, an undocumented free-form query object, and a nested-object parameter shape, the description should explain what the request/response looks like. Instead it delegates entirely to describe_operation, leaving the agent unable to call the tool confidently from this definition alone.

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' as free-form object, 'params' as empty object) are entirely undocumented. The description does not compensate at all — it neither names a query parameter nor explains what query keys are accepted.

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 repeats the endpoint path verbatim twice ('GET /api/rent-adjustment-import/template'), which restates the title rather than explaining what a 'template' is here (file download? JSON schema? CSV headers?). An agent can infer the resource but not the actual effect.

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 versus the sibling get_rent_import_template or get_supplemental_rent_import_targets. The only directional hint is that 'describe_operation provides native request schemas', which is a pointer to another tool 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.