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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the '[read]' prefix adds nothing. Beyond annotations the description contributes no behavioral context: no note on pagination behavior, default page size, result ordering, or what 'connected' implies for account status.

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?

One sentence, front-loaded with the verb and resource, with the filter set trailing as an 'optionally' clause. Nothing is padded and no sentence is wasted.

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?

For a read-only list tool with no output schema and no required parameters, the description is serviceable but thin: it never indicates whether the response is paginated, what fields an account record carries, or how to walk multiple pages. Acceptable, but an agent would still need to open the schema to use pagination.

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 0%, so the description carries the burden, and it partially does: it maps seliee_website_id/seliee_website_uuid to 'website' and names provider and status filters. However, page and per_page are never mentioned and no accepted values or formats (provider slugs, status enums) are given, so roughly a third of the parameters remain unexplained.

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?

States a specific verb (List) and a clearly scoped resource: connected web-analytics accounts, enumerated as GA4 / Yandex Metrica / Clarity. That qualifier separates it from the many other account-list siblings (list_ads_accounts, list_sms_accounts, list_social_accounts), though no sibling is named explicitly.

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 tells the agent which filters exist (provider, status, website), which implies the usage of narrowing a listing, but it never states when to reach for this vs. a reporting tool like get_metric_report or when a listing is unnecessary. Usage is implied rather than stated.

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