get-crm-v3-objects-quotes_quotes

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

With no annotations provided and a one-word description, the tool is completely opaque. It does not disclose whether this is a read-only operation, pagination behavior, response format, or any side effects. For a GET-like tool, the agent is left without essential safety and behavior information.

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 under-specified, not succinctly informative. A single word might be concise, but it omits all necessary context. It does not earn its place because it adds almost no value beyond the tool name itself.

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 six parameters, no annotations, no output schema, and a one-word description. It is completely inadequate for an agent to understand what the tool does, when to use it, or what to expect in the response. The description needs to explain the resource, pagination, and parameter behavior, and it does none of this.

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 input schema has 100% description coverage for all six parameters, so the schema already provides full parameter semantics. The description adds no additional meaning. Baseline 3 is appropriate because the schema does the heavy lifting and the description does not compensate or enhance it.

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 only the word "List", which is a generic verb with no resource identified. It does not state that this tool lists CRM quotes objects, making the purpose extremely vague. It fails to distinguish from the many other list endpoints in the sibling 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 sibling alternatives such as get-crm-v3-objects-quotes-var_var (retrieve a single quote) or post-crm-v3-objects-quotes-search_search (search quotes). The description does not mention exclusions, prerequisites, or alternative use cases, so it provides zero usage context.

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