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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the description does not need to argue safety. It does add value beyond the annotations by disclosing the return shape (titles, short summaries, last-updated dates, links), which matters because there is no output schema, and it flags that geographic details are optional. It does not mention result limits or fallback behavior when nothing matches.

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 search verb and resource, then the topic enumeration, then the usage trigger; every clause carries information. The middle enumeration is long but each item corresponds to a real topic enum value, so it earns its space rather than padding. Slightly dense for a single paragraph but structurally sound.

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 read-only article search with five flat parameters, the definition covers what it retrieves, when to use it, and what comes back, which is enough to call it correctly. Remaining gaps are minor: no guidance on result count or how to behave when zero guides match, and no explicit boundary against the similarly named search_parking sibling.

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 coverage is 60%, so some compensation is required, and the description provides it: it confirms the place/city is optional and effectively maps its topic list onto the topic enum values (free, cheap, costs, fines, towed, disability, permits, signs, street, storage, moving). It adds no detail about limit (default 3, max 5) or the country code, so the low-cost narrowing controls remain schema-only.

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?

Specific verb ('Search') plus specific resource ('Parksy parking guides and articles'), followed by an enumerated subject list (free/cheap parking, rates, fines and appeals, towing, disability, permits, signs, street rules, storage, moving) and the return content. An agent can immediately tell this is an editorial-content search rather than a listing/price lookup like search_parking or a workflow like fine_appeal_check.

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 trigger: 'Use this when a driver asks what to do or what the rules are (towed, clamped, fined, permits, signs)', which is a concrete situation with examples. No when-not condition or named alternative is given, even though siblings search_parking and fine_appeal_check sit close to this space, so the routing decision is not fully disambiguated.

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