cases_list_layouts

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

No annotations are provided, so the description must disclose behavioral traits. It simply says 'List case layouts' with no mention of read-only behavior, output format, pagination, or potential side effects. Even though listing is likely read-only, the description fails to state this, leaving a significant transparency gap.

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 short (one sentence plus a tip), but this brevity comes at the cost of essential information. It is under-specified rather than efficiently concise, missing parameter context and behavioral details that a longer description would provide.

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 a 2-parameter tool with zero parameter descriptions and no annotations, the description is incomplete for safe and correct invocation. The output schema exists but cannot compensate for the lack of parameter semantics. The tip points to layout_visualizer but doesn't fully contextualize when to use this list tool.

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%, and the description provides no information about the required 'domain_id' or optional 'max_results' parameters. An agent cannot infer what domain_id means or how max_results behaves from the tool description alone, so the description adds no value beyond the schema's raw property names.

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 verb 'List' and the resource 'case layouts', making the core purpose obvious. The tip about layout_visualizer helps differentiate this listing tool from the design tool, though it doesn't distinguish from sibling list tools like cases_list_fields or cases_list_templates beyond the resource name.

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 only indirect usage guidance via the tip: if you want to design new layouts, use layout_visualizer. It does not explicitly state when to use this tool (e.g., to view existing layouts before editing) or mention any exclusions or alternatives for listing. The guidance is implied rather than explicit.

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