List Widgets

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the HTTP method and that results are ordered, but it does not mention pagination behavior, response format, or any potential operational details beyond the annotations and schema.

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, front-loaded sentence that includes the HTTP method, resource path, action, scope, and ordering behavior. There is no redundant or filler content, making it appropriately concise.

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 the tool's simplicity, the well-documented schema, and the helpful annotations, the description is mostly sufficient. It lacks explicit information about return value shape or pagination semantics, but the 'list all' phrasing combined with the schema's limit/cursor parameters provides adequate context for an AI agent.

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 100%, with all five parameters documented in the input schema. The description adds no distinct parameter semantics; it only hints at ordering, which is already represented by the order_by parameter. A baseline of 3 is appropriate since the schema carries the parameter documentation burden.

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 states 'GET /api/widgets — List all widgets for the account, ordered.' It uses a specific verb ('List'), identifies the resource ('widgets'), and clarifies account scope, distinguishing it from sibling tools like get_widget, create_widget, update_widget, and delete_widget.

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 clear context: use this tool to list all widgets for the account. It does not explicitly name alternatives or state when not to use it, but the resource name and 'list' verb make the usage context obvious relative to sibling get/create/update/delete widget tools.

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