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

readOnlyHint=true already tells the agent this is a safe read. The description adds real value by disclosing that results come back in a paged envelope, but it does not describe pagination limits, ordering defaults, or whether filters are pushed to the source system — the remaining behavioral gaps are left open.

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 statements: what is listed and the returned fields first, then the endpoint, then the response shape. No filler, and the most important information is front-loaded.

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, single-required-param list tool with full schema coverage, the definition covers identity, returned fields, and response envelope. Without an output schema the field list is a helpful substitute, though ordering/filter semantics and pagination defaults are only in the schema, not elaborated.

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%, so page, pageSize, query, orderBy, and companyId are all documented inline with examples and ranges. The description adds no parameter-level meaning beyond the schema; 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), enumerates the returned fields (id, name, nominalCode, type, status, currency, currentBalance), and gives the underlying endpoint. This clearly separates it from siblings like codat_list_account_transactions and codat_list_journal_entries.

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 purpose implies when it is used (fetching a company's chart of accounts), but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. an existing connection or data sync), and no routing to alternatives such as codat_list_account_transactions. Usage is inferable but not stated.

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