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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantial behavior: excluded record classes (test pages, private events, cancelled or hidden stops), conditional field presence (order_url only when preorders are open for that stop), and the fact that days with no posted stop are omitted entirely.

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?

The core purpose is front-loaded in the first clause, and each following sentence adds distinct information (list semantics, days behavior, exclusions, cities) rather than padding. It is dense and slightly run-on with heavy quoting of field names, but no sentence 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 no output schema, the description carries the full burden of describing return shape, and it does so thoroughly: per-list field inventories, the parks counts, the optional date-grouped 'days' structure, and the exclusion rules. An agent can call and interpret this tool correctly from the definition alone.

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 100%, so the baseline is 3; the description goes beyond it by explaining what 'days' actually does (returns a date-grouped 'days' list covering today plus the next N days) and that empty days are dropped, which is behavior the schema cannot express. City semantics are left to the schema's example values.

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 (get food trucks in one city today) and immediately partitions the output into two named lists with their status values, so an agent knows exactly what it returns. No sibling tool (get_business, get_menu, get_upcoming_events, search_businesses, start_order) covers trucks, so differentiation is inherent and reinforced by the explicit scope.

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 clear context for use: single-city, today local time, with the supported city list (Myrtle Beach, Austin) acting as a usable precondition. It also sets semantic rules ('usually_here' must never be called 'out tonight'), but it never names an alternative tool or states a when-not-to-use condition.

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