get_conversation_notes

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 states the tool 'gets' notes, implying a read-only operation, but does not clarify permissions, rate limits, error handling, or what the output contains. For a tool with no annotation coverage, this is a significant gap in transparency, as critical behavioral traits are omitted.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse. However, it could be more structured by including key details, but it earns high marks for brevity and clarity within its limited scope.

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 has an output schema (which reduces the need to describe return values) but no annotations and low parameter coverage, the description is minimally adequate. It covers the basic purpose but lacks details on usage, parameters, and behavioral context. For a tool with 3 parameters and no annotations, it should provide more guidance to be fully complete, but the output schema mitigates some gaps.

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 0%, meaning parameters are undocumented in the schema. The description mentions 'product scope' and 'CRM conversation,' which loosely relates to 'product_slug' and 'conversation_id,' but does not explain their semantics, formats, or the optional 'client_id' parameter. It adds minimal value beyond the schema, failing to compensate for the coverage gap.

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 states the tool's purpose as 'Get notes for a CRM conversation in a product scope,' which clearly identifies the action (get) and resource (notes for a CRM conversation). However, it does not differentiate from sibling tools like 'get_conversation_by_id' or 'update_conversation_notes,' making the scope somewhat vague. It avoids tautology but lacks specificity about what 'notes' entail or how this differs from similar 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools such as 'get_conversation_by_id' (which might retrieve conversation details without notes) or 'update_conversation_notes' (for modifications), nor does it specify prerequisites or context for usage. This leaves the agent without explicit direction on tool selection.

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