post-crm-v3-objects-quotes-batch-read_read

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

No annotations are provided, so the description must disclose behavior. It does this by highlighting the mandatory body parameter and giving a concrete example, which is valuable. It does not detail response format or idProperty usage, but the verb 'Read' implies a safe operation.

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 and an example. It is front-loaded with purpose and immediately gives actionable invocation guidance without 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?

Given the tool's complexity, the description is fairly complete with the example and mandatory body note. The lack of output schema means return format is not described, but this is a minor gap for a read operation.

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 descriptions are generic and even misleading (e.g., properties described as 'setting properties'), but the description adds meaning by explaining that inputs contain object IDs and properties are fields to retrieve. The example clarifies the structure beyond the 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 the tool reads a batch of quotes by internal ID or unique property values. This specific verb+resource+method distinguishes it from siblings like batch create/update/archive and single quote read.

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?

It provides clear context for use: reading multiple quotes by IDs or unique properties. However, it does not explicitly name alternatives (e.g., search) or state when not to use this tool.

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