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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful scope context (six-city directory, filterable dimensions, drill-down path) but says nothing about result shape or pagination behavior, and there is no output schema to fill that gap.

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?

Three short, front-loaded blocks with bracketed labels that let an agent scan purpose, primary use case and drill-down target immediately. No filler sentences; the only prose addition ('highest-frequency need') justifies why the example filter matters.

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?

Covers the primary filter semantics and the follow-up tool for a 7-param, no-output-schema listing tool, with annotations carrying the safety profile. The remaining gap is result shape and pagination behavior, which neither the description nor an output schema explains.

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%, so the baseline is 3, but the description adds real semantic value: it tells the agent how to use benefitType in practice (RENT_SUBSIDY → parks with rent subsidy) and that filters stack with city/track/status/keyword. That is meaning beyond the enum definitions in the schema.

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+resource+scope: '浏览/筛选 OPC 园区目录（六城）'. It also explicitly distinguishes itself from the sibling get_park, which it positions as the drill-down step rather than a duplicate listing tool.

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?

Gives an explicit highest-value usage path (filter by benefitType=RENT_SUBSIDY) and names the combinable filters (city / track / status / keyword). It also states when to escalate to get_park for subsidy details, occupancy conditions and sources, so the routing decision is fully specified.

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