ep_batch_submit

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

No annotations are provided, so the description must fully disclose behavioral traits. It claims atomic submission but also says 'returns per-receipt success/failure,' creating ambiguity about whether the operation is truly all-or-nothing or allows partial success. It does not mention side effects, authentication requirements (beyond implicit API key), rate limits, or error handling for batches exceeding the limit. The transparency is insufficient for safe agent invocation.

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 concise: three information-dense sentences. The first sentence states the action and atomicity, the second adds submitter context, the third gives use cases and return behavior, and the fourth provides a limit. No extraneous text; every sentence is necessary and well-placed.

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 the tool's moderate complexity (array input, batch operation) and lack of output schema, the description provides a basic return structure ('per-receipt success/failure') but does not specify the exact format (e.g., array of objects with receipt ID and status). It also does not explain error scenarios for invalid receipts or exceeding the limit. More detail would improve completeness.

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 description coverage is 100% since the only parameter 'receipts' is described in the schema. The description adds that the receipt objects follow the same schema as 'ep_submit_receipt,' which is helpful context. However, it does not elaborate on the meaning of individual subfields or provide examples. This meets the baseline for high coverage but adds no significant extra value.

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's purpose: submitting multiple receipts atomically. It distinguishes from single receipt submission by noting that all receipts share the same submitter (API key) and specifies a maximum of 50 receipts per batch. It also mentions use cases, reinforcing the purpose.

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 explicitly identifies use cases ('bulk reconciliation or recording a session of agent-entity interactions'), which helps the agent decide when to use this tool. While it doesn't explicitly say when not to use it, the context of batching versus individual submission (sibling tool ep_submit_receipt) is implied. Missing explicit alternatives or exclusions.

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