List Account Settings

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavioral details: it returns an array of AccountSetting objects, does not support pagination, and supports filtering by type. This goes beyond what annotations provide.

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 two sentences, front-loaded with the endpoint and purpose. Every phrase carries information: the response type, pagination behavior, and filter capability. No redundant words.

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?

The description clearly covers the core behavior: listing all settings, the optional filter, and the return type. Without an output schema, it does not detail the AccountSetting object structure, but for a simple list tool with one optional parameter, the information is sufficient for an agent to call it correctly.

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 schema already provides a detailed description of the 'type' parameter, and the description's statement 'Supports filtering by type' adds no new meaning. With 100% schema coverage, the baseline of 3 is appropriate.

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 HTTP method and resource path ('GET /api/account/settings') and the action ('List account settings'). It distinguishes this read-only listing tool from sibling tools like create/update account setting by its verb and scope.

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?

It specifies the scope ('for the current account') and explicitly notes the lack of pagination, telling the agent that a single call returns all settings. It also mentions filtering by type, which provides usage context. It does not explicitly contrast with create/update alternatives, but the purpose is self-evident.

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