list_quality_definitions

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

No annotations are provided, so the description carries the burden. It clearly indicates this is a read-only listing operation, specifies the output content (size limits in MB/minute), and explains the real-world meaning of the data. This is sufficient for a simple list tool with no visible side-effects or external dependencies.

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?

Two short sentences with no filler. The primary action and resource are front-loaded, and the clarifying note about size limits and release rejection adds meaningful information without unnecessary detail.

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?

For a no-parameter, read-only list operation with no output schema, the description is largely complete: it states what is returned and what the values mean. It does not explicitly state the return format (e.g., an array of objects), but 'List' strongly implies that, and no other usage context is missing.

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 tool has zero parameters and the schema has no properties, so there is no parameter documentation burden. The baseline for zero-parameter tools is 4, and the description appropriately focuses on the output semantics instead.

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 uses the specific verb 'List' with a clear resource ('quality definitions') and adds substantive context about size limits and what these definitions do (reject releases as too small/large). It does not explicitly contrast with sibling tools like list_quality_profiles, but 'quality definitions' is distinct enough that an agent can identify the intended resource.

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 implies when to use this tool (when you need quality definitions and their size limits) and explains the purpose of the returned data. However, it does not provide explicit guidance on when not to use it or which sibling tool might be a better fit, so usage context is only implied.

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