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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: Track-POD returns the whole day in one payload while this tool pages it via offset/limit and reports a total, plus that times are the account's local times. Rate limits and partial-failure behavior remain unstated.

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 dense sentences, purpose front-loaded, then paging behavior and the timezone caveat. No filler, and the parenthetical endpoint paths give concrete grounding without bloating the text.

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 listing tool with no output schema this covers the essentials: scope (one day), two endpoint modes, filter dimensions, paging mechanics and total reporting. The absence of any return-shape hint is the only real gap, and the schema's detail enum partly compensates.

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?

With 100% schema description coverage the schema already documents all 8 parameters, so the baseline is 3. The description adds value beyond it by framing date semantics against the two endpoints and noting times are in the account's local timezone, which the schema never states.

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 ('List the orders of one day') and immediately scopes it to the two backing endpoints (by order date vs. planned route date). This distinguishes it cleanly from siblings like trackpod_list_orders_changed_since and trackpod_list_route_orders without needing to open any 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?

The description makes the core selection context explicit: one specific day, with the order-date vs. route-date choice that drives date_type. It does not, however, name sibling alternatives (e.g. find_orders_by_number, list_route_orders) or state when this tool is the wrong choice, so routing is clear but not fully disambiguated.

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