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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the underlying endpoint, the returned linked entities (tenant, unit, property, full complaint text), the 'Resident Concern' issue scoping, and the newest-first ordering.

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?

Front-loaded with the core capability and the sibling contrast, then filters, then example queries. Slightly long, but each block—contrast, data payload, filters, triggers—carries distinct information, so little is wasted.

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 an output schema present, return-value detail is not needed, and annotations cover the safety profile. The description supplies source, payload contents, ordering, and filter semantics, leaving only the limit param unexplained—a minor gap for a 7-param, read-only tool.

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%, so the description carries the parameter burden and mostly delivers: it explains property (name or short code), status, priority, and the start_date/end_date window with accepted formats (M/D/YYYY or ISO). It only leaves limit and the open_only toggle unaddressed, though 'open resident complaints' hints at open_only's default behavior.

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 and resource (open resident complaints) and immediately distinguishes itself from key sibling analyze_service_issues by data source (report 112 vs. /ServiceManagerIssues) and by carrying resident contact data. An agent can tell them apart without opening either schema.

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?

Explicitly names the alternative (analyze_service_issues) and the reason to prefer this one (contact data for drafting replies), and seeds concrete trigger questions like 'who complained at <park> and how do I reach them'. When-to-use and when-not are both covered.

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