list_clients

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

Without annotations, the description carries full burden and effectively discloses that the tool returns different results based on account type (reseller vs single-account) and supports an optional partial name search. No hidden behaviors are implied.

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 with no unnecessary words. It front-loads the main purpose and immediately specifies the scope. Every phrase adds value.

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 simple tool (one optional parameter, no output schema), the description adequately covers the two key behaviors (reseller vs single-account) and leaves no major gaps for an agent to understand what the tool does.

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 covers the only parameter with a description ('Optional partial name search'), and the description adds the context that it is for searching by partial name. Since schema coverage is 100%, baseline is 3; description adds minimal new semantic value.

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 'List clients (for reseller accounts)' and explains the distinction between reseller (returns all clients) and single-account keys (returns current client). This verb-resource pair is specific and distinguishes from sibling tools like list_posts or list_media.

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 clarifies when to use this tool: for listing clients under a reseller or for single-account keys. It does not explicitly mention when not to use it or name alternatives among siblings, but the context of 'clients' is clear and distinct.

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