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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds the return contents and the underlying GET endpoint, but says nothing about pagination behavior, result caps, or default ordering beyond what the schema already provides. Adds some value but not rich behavioral context.

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?

Two tight sentences, front-loaded with purpose followed by filter scope and endpoint mapping. Nothing is redundant or padded; every clause carries information.

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, the description responsibly notes the returned payload (contact details, status, applications), and all 13 parameters are documented in the schema. Annotations cover the read-only safety stance. Only the omission of paging/ordering behavior and when-not-to-use guidance keeps it short of complete.

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 100% across all 13 parameters, so the schema does the heavy lifting and the baseline is 3. The description mirrors several filter names (status, unit, name, email, submission date, entity) but adds no format or constraint detail beyond the schema, and omits limit/offset/orderby entirely.

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 specific verb (List) and resource (rental applicants), and even names what the records contain (contact details, status, applications). It also maps to the API endpoint. No sibling of this list family competes for 'applicants', so differentiation is implicit rather than stated.

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?

The description enumerates the filterable dimensions (status, unit, name, email, submission/update date, entity), which implies how to narrow results, but it never states when to prefer this over related lookups (e.g. list_tenants) or any conditions/exclusions. Usage is implied, not prescribed.

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