get-crm-v3-objects-invoices-var_var

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. 'Read' says nothing about whether this is a safe read operation, required permissions, side effects, pagination, response format, or error behavior. It discloses nothing beyond the HTTP method.

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?

One word is extreme under-specification, not conciseness. There is no useful information to be front-loaded, and the description fails to earn its place as a meaningful tool description.

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?

For a tool with six parameters, a required invoiceId, no output schema, and no annotations, the description is completely inadequate. It does not explain what the tool returns, how parameters interact, or any filtering/selection behavior. The schema exists but the description adds no contextual glue.

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 100% with detailed descriptions for all six parameters, so the baseline is 3. The description adds no parameter-level value, but the schema fully compensates, so a 3 is appropriate.

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 is the single word 'Read', which is a tautology of the HTTP GET verb and provides no specific information about what resource is being read. It does not distinguish this tool from the many sibling tools for invoices, quotes, line items, etc.

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?

There is no guidance on when to use this tool versus alternatives such as get-crm-v3-objects-invoices_invoices (list) or post-crm-v3-objects-invoices_invoices (create). No context or exclusions are provided.

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