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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds genuine value by disclosing that a call returns a single page rather than all matching records, which tells the agent it must paginate to be exhaustive — a behavioral trait not derivable from the annotations.

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 sentences, no filler, with the content summary first and the pagination caveat second. Every clause carries information an agent can act on.

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?

Six optional parameters and no output schema, but the schema itself documents each parameter thoroughly and the description covers the key non-obvious behavior (pagination). Only minor gaps remain, such as whether a total count is returned or how filtering interacts with paging.

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 100%, with limit, pageIndex, fields, wField, wValue and wOperator all documented in-schema including defaults and pairing constraints. The description adds nothing about parameters, so the baseline 3 applies.

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 the resource (customer accounts), the returned content (names, contact details, account status), and the underlying endpoint GET /v1/accounts. This clearly reads as a paged collection fetch, distinguishable from get_account, though it never names that sibling 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?

No statement of when to use this versus get_account or get_account_profile, and no guidance on when filtering with wField/wValue is appropriate. The only usable cue is the 'one page, not all matching records' note, which implies iteration but does not say when this tool is the right choice.

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