post-crm-v3-objects-invoices_invoices

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that a body parameter is required, but does not mention side effects, idempotency, authentication needs, or response behavior. This is insufficient for a mutation tool.

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 short, but it is under-specified rather than concise. It does not provide enough information to be useful, and the phrase 'REQUIRES body parameter' is redundant with the schema's required field. It lacks meaningful content despite its brevity.

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?

The tool has a nested schema, no output schema, and complex sibling relationships. The description does not explain return values, required properties semantics, or how this relates to other invoice operations like batch-create or search. Reliance on the schema alone is inadequate for the complexity.

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?

The schema description coverage is 100% and includes meaningful descriptions for the parameters (e.g., properties key-value pairs and association structure). The description adds no parameter information other than pointing to the schema, which meets the baseline for high coverage.

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 says 'Create' which indicates an action but does not state what resource is being created. The name contains 'invoices' but the description itself lacks specificity, making it vague and indistinguishable from other object creation tools like those for quotes or line_items.

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 is provided on when to use this tool versus alternatives. It does not mention batch create, upsert, or any context that would help an agent select this over sibling tools. The only note about required body is a requirement, not a usage guideline.

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