get-crm-v3-objects-line_items-var_var

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

With no annotations and a one-word description, the tool's behavior is entirely undisclosed. The agent cannot infer that this is a safe read operation, whether it returns archived items by default, or any permissions or side effects. The description adds zero behavioral context.

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 the description is brief, it is under-specified rather than concise. A single word 'Read' does not constitute a helpful description; it omits essential information that could be conveyed in a few sentences.

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 no annotations, no output schema, and a one-word description. For a GET-by-ID operation, the agent needs to know what response format to expect, whether archived records are included by default, and how to handle optional parameters. The description is completely inadequate for safe 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 description coverage is 100%, so the schema fully documents all six parameters. The description 'Read' adds no additional meaning beyond the schema. Per the rubric, baseline 3 is appropriate when the schema carries the parameter documentation burden.

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 'Read' is a tautology of the HTTP GET method implied by the tool name. It gives no indication of the specific resource (line items) or the operation's scope, and it fails to distinguish this tool from the many sibling read tools.

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. The description does not mention the required lineItemId or any context for when a single-line-item read is appropriate, nor does it reference batch reads or search as alternatives.

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