List Zendesk views

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

readOnlyHint already indicates no side effects. Description adds that views are 'active' and include 'cached ticket counts', which is behavioral context.

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 concise sentences with essential info.

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?

Despite lack of output schema, description covers return fields and links to related tool. Sufficient for a zero-parameter 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?

No parameters in schema, description doesn't need to add param info. It describes output which aids understanding.

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?

Specifies verb 'list', resource 'ticket views', and details returned data: numeric IDs, titles, cached ticket counts. Differentiates from sibling zendesk_fetch_view_tickets by stating usage.

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?

Mentions using returned id with zendesk_fetch_view_tickets, providing clear context for subsequent action. No explicit when-not, but tool is single-purpose.

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