Get pickup schedule (days + time window)

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds valuable context: it explicitly states Crown Town Compost publishes no guaranteed arrival window, so the window is empirical and derived from recorded collection times. This explains the tool's behavior and data provenance, exceeding what annotations alone convey.

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 description is two concise sentences, front-loaded with the primary outcome and enriched with necessary caveats. Every sentence contributes meaning, with no redundant or filler content.

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?

Despite lacking an output schema, the description enumerates exactly what is returned (pickup days, next service date, set-out time, observed window with earliest/latest/typical and consistency). It also covers the empirical derivation and absence of guaranteed times, making the tool's behavior fully understandable in context.

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?

The input schema fully documents history_sample with a clear description, type, default, and bounds. The tool description does not mention the parameter, but since schema coverage is 100%, the baseline of 3 is appropriate; no additional semantic value is needed.

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?

The description clearly states the tool fetches the pickup schedule for each service address, listing the exact elements returned (pickup days, next service date, set-out time, observed arrival window). This specific verb+resource combination distinguishes it from sibling tools like list_upcoming_services, which focus on individual upcoming services rather than the recurring schedule.

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 gives clear context on what the tool returns, implying when to use it (when you need the schedule and arrival-time window). It does not explicitly name alternatives or exclusions, but the behavioral detail about the observed window makes its purpose obvious relative to siblings.

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