sophos_list_quotes

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds value by specifying that only approved quotes are returned, which is a key behavior not in the annotations. It does not mention pagination or rate limits, but for a read tool, this is adequate.

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 two sentences long, front-loads the core purpose, and contains no filler or redundant information. Every word adds value.

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?

The tool has many optional filters (14 parameters) and no output schema. The description does not explain typical usage patterns or the return structure (e.g., paginated list). The schema partially compensates with detailed parameter descriptions, but completeness is moderate.

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, so all parameters are documented. The description only repeats the requirement for distributor_id, which is already in the schema. It does not add extra semantic value beyond what the schema provides.

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 action ('List distributor quotes'), the resource ('distributor quotes'), and constraints ('Only approved quotes are returned', 'Requires a Distributor ID'). It effectively distinguishes from the sibling tool sophos_get_quote and sets clear expectations.

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 mentions that only approved quotes are returned and that a distributor ID is required, but it does not explicitly state when to use this tool instead of alternatives (e.g., sophos_get_quote for a single quote). The guidance is implied but incomplete.

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