chase_bills

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

No annotations are provided, so the description must carry the burden. It states it's a 'get' operation (read-only), but does not disclose any behavioral traits such as authentication requirements, caching behavior, or scope limitations. For a simple retrieval, this is minimally adequate.

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?

Single, front-loaded sentence of 8 words: 'Get bills and payees set up in Chase Bill Pay.' No wasted words, efficient and direct.

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?

Given no parameters and no output schema, the description could be more complete by hinting at the output structure or data fields. It tells what it retrieves but not what the response contains, leaving the agent to infer. Adequate for a simple tool but not comprehensive.

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?

Input schema has zero parameters and schema description coverage is 100% (default). The description does not need to add parameter info since none exist. Baseline is high, and the description correctly implies no input 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?

Description clearly states the tool retrieves bills and payees set up in Chase Bill Pay, with specific verb 'Get' and resource 'bills and payees'. It easily distinguishes from sibling tools like chase_accounts and chase_bill_pay_preview by focusing on the already-set-up items.

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 explicit guidance on when to use this tool versus alternatives like chase_bill_pay_preview. Usage is implied: use when you need the list of existing bills/payees, but no exclusions or context are provided.

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