list_receipt_jobs

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

Lacking annotations, the description only states it returns a JSON array but provides no details on job lifecycle, filtering, pagination, or authentication requirements. Minimal behavioral disclosure for a read operation.

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?

Extremely concise: two sentences, no redundant information. Key purpose and return format are stated upfront.

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?

While an output schema exists and no parameters are needed, the description omits aspects like result ordering, error behavior, or scope (all jobs ever vs. recent). Sufficient for a basic understanding but incomplete for nuanced selection.

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?

No parameters exist, so schema coverage is trivially 100%. The description adds no parameter details, but none are needed. Baseline 3 applies as per rules.

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 action (list) and resource (async receipt extraction jobs), distinguishing it from siblings like get_receipt_job (single job) and get_receipt_job_result (result retrieval).

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 get_receipt_job or extract_receipt_async. Explicit when-to-use or when-not-to-use is missing.

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