List PowerOffice general ledger accounts

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

Annotations already declare the operation safe, read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond annotations by revealing pagination behavior, the exact endpoint, and support for account range syntax like '1000-1999,2500,3000-'.

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 with no filler. The core action and resource are front-loaded, and the account range example is the only extra detail provided, all of which is useful.

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?

Between the description, the read-only annotations, the output schema, and schema parameter descriptions, the tool is mostly self-sufficient. The main gaps are lack of routing guidance to sibling tools and no explanation of ambiguous parameters like useDatabaseValidation, but this is not critical for a read-only list operation.

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?

The schema already provides descriptions for 63% of parameters. The description adds valuable semantic context for accountNos by showing concrete syntax examples, and clarifies pagination behavior which helps interpret pageNumber and pageSize. A few schema-uncovered parameters like useDatabaseValidation remain unexplained, but the description is not solely responsible since coverage is above 50%.

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 description uses a specific verb ('Read'), a specific resource ('GET /GeneralLedgerAccounts'), and states it returns a paginated list. This clearly differentiates it from creating/updating general ledger accounts and from listing account transactions.

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 description implies the tool is for reading a paginated list of general ledger accounts, but it does not explicitly state when to use this tool versus alternatives such as create/update_general_ledger_account or list_account_transactions. There is no 'when not to use' or sibling-specific routing guidance.

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