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

readOnlyHint=true already declares this is a safe read. The description adds the underlying Buildium endpoint and the shape of returned records, but says nothing about result size, paging behavior, or rate limits beyond what the schema states. Reasonable but not rich.

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 tight sentences: scope, use case, endpoint. The resource scope is front-loaded and no sentence is filler.

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?

With annotations covering safety and the schema covering paging/sorting, the description is nearly complete; listing return fields compensates for the absent output schema. Minor gap: no explicit note on default page size or how to fetch all accounts.

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 limit, offset, orderby and account_types are already fully documented. The description names account attributes but adds no syntax or filtering semantics for the parameters themselves; 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?

Specific verb (List) + resource (chart of accounts / GL accounts), and it enumerates the returned fields (number, name, type/subtype, sub-accounts, flags), which no sibling provides. An agent can distinguish it from buildium_list_bills or buildium_list_lease_transactions immediately.

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 downstream use case ('finding the gl_account_id for work order line items'), which tells the agent when this tool is the right call. It stops short of naming alternatives or stating when-not to use it, so it falls short of a 5.

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