List purchase schedule

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

Annotations already declare readOnlyHint and idempotentHint, reducing the need for behavioral disclosure. The description adds context about the data source but omits details on pagination behavior, empty results, or authorization requirements.

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 a single concise sentence that communicates the core purpose efficiently. It is front-loaded with the action and resource, but could benefit from slight expansion to cover key parameters.

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 and 9 undocumented parameters, the description lacks sufficient detail about input options and return format. Agents cannot infer what fields are returned or how to filter effectively.

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 0%; none of the 9 parameters are described in the schema. The description provides only a vague hint about filtering ('from monthly budget entries and split schedules') and does not explain any specific parameter's meaning or usage.

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 specifies the action ('list') and resource ('scheduled budget purchases') and distinguishes from sibling list tools by mentioning 'from monthly budget entries and split schedules', but could be more precise about what a purchase schedule includes.

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?

No guidance on when to use this tool versus alternatives like other list_* tools. The description lacks context on prerequisites or cases where this tool is appropriate.

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