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 externally. The description adds no behavioral context beyond that — no return shape, no pagination, no auth or rate-limit notes. Since the bar is lower with annotations, this is a modest gap rather than a failure, but nothing is contributed.

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 first sentence is duplicated verbatim and the second duplicates the title. Almost no sentence earns its place — the entire content could be one line of genuine description.

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 a nested free-form query object, an empty params object, no output schema and zero parameter documentation, the description leaves an agent unable to construct a correct call without first invoking describe_operation. The offload pointer is at least honest, but the definition is not self-sufficient.

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, params) are free-form objects with no documented properties. The description does not describe any parameter semantics; it only points to describe_operation as the place to obtain native schemas, which is a delegation rather than an explanation.

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 the HTTP verb and path repeated twice with no elaboration of what an 'import target' actually is or what the call returns. It effectively restates the name/title, so an agent learns only that this is a GET on the supplemental-rent import-targets endpoint. It does not distinguish this from the many sibling supplemental-rent tools in any meaningful way.

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 guidance on when to call this versus siblings such as get_supplemental_rent_portfolio or the get_leases_by_leaseId_supplemental_rent_* family. The only hint is that describe_operation provides native request schemas, which is a schema-discovery pointer rather than a use-case condition.

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