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

readOnlyHint=true already signals a safe read, and the description adds real value on top by listing the shape of the returned records and naming the backing endpoint (GET /v1/glaccounts). With no output schema, this return-content disclosure is the main behavioral signal an agent needs, though pagination behavior is left entirely to 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?

Three short sentences, front-loaded with what is listed, followed by the use case and the endpoint mapping. Nothing is padded, though the raw endpoint reference is of marginal value to an agent that already sees the tool name.

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, no-required-parameter list tool with full schema coverage and annotations covering safety, the description is nearly complete: it says what is returned, why to call it, and what endpoint it maps to. Only explicit paging behavior is missing, and that is inherited from the schema.

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% -- limit, offset, orderby, and account_types all carry their own documentation, including defaults and the enum values. 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 a specific verb (List) and resource (chart of accounts / GL accounts) and even enumerates the fields returned: number, name, type/subtype, sub-accounts, and bank/credit-card flags. It is unambiguous and easily separable from the other list_* siblings, none of which touch the GL chart of accounts.

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?

Gives a concrete use case -- finding the gl_account_id needed for work order line items -- which tells the agent when this tool belongs in a chain. It offers no explicit when-not or named alternative, but no sibling overlaps in scope, so the guidance is sufficient in practice.

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