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

The annotations already mark this as read-only, open-world, and non-destructive. The description adds meaningful behavior beyond that: it requires an agency key and explains the non-obvious default date filtering that can otherwise hide accounts. It does not cover rate limits or response pagination, but those are partly handled by the 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 front-loaded and compact, with no wasted sentences. It delivers the prerequisite, the returned fields, the downstream use case, the date caveat, and the endpoint efficiently.

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 list operation, rich input schema, and lack of an output schema, the description is complete enough. It covers authentication scope, returned profile fields, intended use of ids, and a critical date-filtering caveat.

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 the baseline is 3. The description adds high-value semantics for start_date/end_date that the schema does not fully convey: WhatConverts defaults start_date to today, so an early date is required to see all accounts.

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 gives a specific verb and resource: list accounts (clients) of the agency, including profile fields. It is clearly a list operation, but it does not explicitly distinguish itself from sibling tools such as whatconverts_get_account or whatconverts_list_profiles.

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 states the agency-key prerequisite and a concrete use case: the returned ids are used to filter leads. It also warns that start_date defaults to today, so an early start_date is needed to list everything. It lacks an explicit statement of when not to use the tool or which sibling to use instead.

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