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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing that credentials are never returned, which is a security-relevant behavior not captured in the structured metadata.

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?

Two short clauses with no filler, and the key read-only marker plus credential caveat are front-loaded. Brevity is appropriate, though it tips into under-specification rather than optimal economy.

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 rich annotations but no output schema, the description should indicate the shape of returned records and how paging works; it does neither beyond the credentials note. Adequate to call safely, but incomplete for interpreting results.

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?

Two pagination parameters (page, per_page) have 0% schema description coverage, and the description says nothing about them, so there is no documentation of defaults, ranges, or pagination semantics anywhere. The description does not compensate for the coverage gap.

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 fragment "Phone provider accounts of the merchant" identifies the resource and, with the name/title, implies a listing operation. However, it never forms a sentence with an explicit verb and does not distinguish itself from nearby siblings such as list_voip_numbers, list_voip_assistants, or list_voip_campaigns.

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?

No when-to-use guidance and no mention of alternatives. An agent must infer from the name alone that this lists account/credential records rather than phone numbers, assistants, or campaigns, all of which have their own sibling tools.

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