save_bill_import

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

No annotations are present, so the description carries the full burden. It does disclose the upsert semantics (update when primary key is present) and a caveat about 'no snapshot data', but it does not clarify what happens to existing data in an update, whether updates are partial or full replacements, or any permission requirements. For a mutation tool, this is a significant gap; the agent is left uncertain about the tool's side effects beyond the basic upsert hint.

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 extremely concise—two short sentences that front-load the main action, endpoint, upsert condition, and the key note about the entity field. Every sentence adds value, and there is no redundant or filler content. It is well-structured for quick agent consumption.

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 has one free-form object parameter, no output schema, and no annotations, the description should provide enough guidance to call it correctly. It mentions the endpoint and upsert behavior, but it does not explain the required structure of the billImport record or what the server contract expects. The agent would likely need external knowledge about the API contract, leaving the description incomplete for safe and correct invocation.

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 100% since the entity parameter has a description ('bill import record object'). The tool description adds meaningful context beyond the schema by explaining that the entity is the billImport record, that no snapshot data should be included, and that it should be passed per the server contract. This helps the agent understand the intent of the free-form object even though the schema itself is generic.

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 action 'add or update bill import record' with a specific resource (bill import) and the upsert behavior based on primary key presence. It distinguishes this tool from siblings like save_bill and save_bills by focusing on the import record domain, leaving no ambiguity about what resource it acts on.

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 provides no explicit guidance on when to use this tool instead of alternatives like save_bill or save_bills. It implies usage through the 'bill import' context, but there is no stated exclusions, prerequisites, or comparisons. The agent must infer when to select this tool based solely on the name and resource type.

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