listWidgets

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

Annotations (readOnlyHint=true, idempotentHint=true) are consistent. The description adds pagination details (cursor-based, limit, page), filter/sort operator semantics, and return format. No contradictions; extra behavioral context is provided beyond annotations.

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?

Well-structured with clear sections (Use when, Pagination, Filter/sort, See also, Returns). The field table is verbose but valuable. Slightly long but every part serves a purpose; front-loading of key points is good.

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?

No output schema, but the description provides complete return structure and each field. Covers pagination, filtering, sorting, and alternatives. References external rules for pagination and filter operators. Highly thorough for a 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 coverage is 100%, so baseline 3. The description explains how filter/sort parameters work in practice (e.g., 'property_operator' word forms, date operators) and references rules for operators. It also provides a full field table for return values, indirectly clarifying parameter use. This adds value above the schema descriptions.

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 explicitly states it lists widgets with paginated enumeration, describes widget use cases (embedding in pages via shortcode or email templates), and distinguishes from getWidget (single by ID) and create/update/delete siblings. This provides a clear, specific verb-resource-purpose statement.

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?

Clear guidance: 'Use when' discovering widgets for pages/emails; explicitly redirects to getWidget for fetching by ID. Mentions useful filter 'widget_viewport=front' and references filter/sort rules. Exclusions and alternatives are well-covered.

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