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

Annotations declare readOnlyHint=false and idempotentHint=false, so this is a non-idempotent mutating call, but the description says nothing about what it creates or changes, whether it emits a proof/record, or what data must be supplied. With no annotations on auth or rate limits and no descriptive follow-through, the agent lacks the behavior profile needed to call it safely.

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 a single short sentence with the verb front-loaded and no bloated preamble, which is good. But the second half ("proof-ready housing decisions") is filler that consumes the only descriptive budget without informing the caller.

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 non-idempotent write tool with no output schema and a request body whose contract is only pointed at externally, the description is far too thin. It omits required inputs, the nature of the result, and any prerequisites, leaving the agent unable to invoke it confidently.

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?

There is a single body parameter with 100% schema description coverage, so the baseline is 3. The description adds no detail about the body's required fields; it instead defers entirely to "the AffixIO OpenAPI schema resource," which is a dangling reference rather than added meaning.

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?

States a verb ("Check") and a resource ("rental eligibility"), which is enough to know it's an eligibility check tool. However, "proof-ready housing decisions" is marketing phrasing that adds no discriminating detail, and the description never distinguishes it from the sibling rent_catalogue, which an agent must choose between.

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 when-to-use guidance, no preconditions, and no mention of the obvious alternative (rent_catalogue, or other *_check tools like stay_check/finance_check). The agent must infer context from the name alone.

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