post-crm-v3-objects-invoices-batch-read_read

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Read' but does not explicitly confirm read-only behavior, auth requirements, rate limits, or response format. This is a significant gap for a tool with zero annotation coverage.

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: two sentences plus an example. The purpose is front-loaded, and the example is directly useful without unnecessary fluff.

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 description covers the 'what' and 'how' with an example, but omits return value details, error behavior, batch size limits, and interaction with the 'archived' parameter. Given there is no output schema and no annotations, these omissions leave the description incomplete for a production tool.

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?

Although the schema already covers all parameters (100% coverage), the description adds a concrete request-body example showing how to structure inputs, properties, and propertiesWithHistory. It also hints at idProperty via 'unique property values', adding practical value beyond the raw schema.

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 'Read a batch of invoices by internal ID, or unique property values' – a specific verb, resource, and method. It distinguishes from sibling batch-read tools by specifying the 'invoices' object type.

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 implies usage when you have known invoice IDs, but it does not explicitly mention alternatives (e.g., search vs. batch-read) or exclusions. There is no when/when-not guidance beyond the implied batch context.

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