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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so 'Read-only' in the description is largely redundant. However, the explicit exclusion list (credentials, application numbers, income, household details, email, internal identifiers) is genuine added context about the data surface that annotations cannot convey.

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 short sentences with zero filler, and the scope statement is front-loaded ahead of the privacy qualifier. Every clause adds 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?

An output schema exists, so return-value shape need not be explained, and the description covers scope plus data exclusions. The remaining gap is pagination/limit behavior, which matters for a list tool but is a minor omission given the annotations and output schema.

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 the description says nothing about the single 'limit' parameter, its default of 20, or the 50-item ceiling. Since the tool does take a parameter, the description should have compensated for the silent schema but does not; only the schema's own bounds/default carry any 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 specific verb (List) and a precisely scoped resource (the connected renter's provider-confirmed NYC Housing Connect application statuses). No sibling tool touches Housing Lottery applications, and the 'provider-confirmed' qualifier further narrows what is returned, so an agent can place it immediately.

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 statement, no prerequisites, and no mention of alternatives such as list_alerted_listings or list_upcoming_matches. The 'connected renter's' phrasing implies whose data comes back, but the agent must infer the usage context entirely.

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