list_catalog_item_variables

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

Annotations are absent, so the description carries the full burden of disclosing behavior. It does not mention that the operation is read-only, the response format, pagination semantics of limit/offset, error handling, or permission requirements. Only the basic act of listing is stated.

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, direct sentence that front-loads the key action 'List' and the resource. There is no fluff or redundancy, making it efficient and easy to parse.

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 tool with three parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the response contains, how limit/offset affect results, or what happens when the catalog_item_id is invalid. The description alone is insufficient for an agent to call the tool correctly and interpret results.

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 description does not reference any parameters. With schema description coverage at only 33% (only catalog_item_id has a description), the description fails to compensate for the undocumented limit and offset parameters. No additional meaning beyond the schema is provided.

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 a specific verb ('List') and a specific resource ('variables (form fields) defined on a catalog item'), making the purpose clear. It implicitly distinguishes from sibling tools like create_catalog_item_variable and update_catalog_item_variable by using the 'list' action, but does not explicitly name alternatives.

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?

No usage guidance is provided. The description states only what the tool does, with no mention of when to use it versus other tools, prerequisites, or scenarios where it should not be used. Agents receive no routing information.

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