books_bulk_export_bills

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

With no annotations, the description carries the full burden of disclosing behavior, but it only states 'Export bills in bulk' without describing output format (e.g., file download, email generation), side effects, or data scope. The schema hints at export_type with pdf/csv/xls options, but the description gives no behavioral context whatsoever.

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?

While extremely short, the description is under-specified rather than effectively concise. The single phrase does not convey any operational details and fails to earn its place as a useful description, so its brevity is a deficiency not a virtue.

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?

This tool has 7 parameters, no annotations, and no output schema, yet the description is a bare five-word sentence. It lacks essential context such as what 'bulk export' produces, how filters interact, and what formats are available, making it completely inadequate for correct tool selection and 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 0% and the description mentions none of the 7 parameters. It does not explain the meaning of export_type, filter_by, date ranges, or search_text, leaving the agent to infer everything from bare parameter names, which is insufficient.

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 'Export bills in bulk' is a direct paraphrase of the tool name 'books_bulk_export_bills' with no added specificity. It identifies the resource and action but fails to clarify what 'export' entails or differentiate from sibling tools like books_bulk_print_bills or books_bulk_export_credit_notes. This is essentially a tautology that adds no new information.

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 usage context is provided. The description does not explain when to choose this over alternatives such as books_bulk_export_credit_notes or books_bulk_print_bills, nor does it state any prerequisites, intended use cases, or exclusions.

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