clio_create_bill

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

No annotations are provided, so the description carries full burden. It only adds routing details (JWT, tenant, company scope) but does not disclose side effects, permissions, rate limits, or what the 'create' operation entails beyond the name.

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 short (4 lines) and front-loads the name. However, the 'Args' section is redundant given the schema, and routing details are standard. It could be trimmed without losing value.

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?

Despite having an output schema, the description fails to explain the purpose or content of the JSON arguments. For a create operation, this is incomplete—agents need to know what fields to include. Sibling tools like billcom_create_bill or xero_create_bill don't affect this tool's own description adequacy.

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 0%, and the description only says 'arguments: JSON string of arguments for the connector operation.' This adds marginal meaning but does not specify the expected JSON structure or fields, leaving the agent with significant ambiguity.

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 states 'create_bill' and mentions it's a Clio connector operation, making the verb and resource clear. However, it does not differentiate from siblings like clio_list_bills or explain what a bill represents in Clio (e.g., invoice, time entry).

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. No prerequisites, exclusions, or context provided. Many clio_* siblings exist, but the description offers no usage direction.

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