List PowerOffice account transactions

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds behavioral context beyond the annotations by noting the inclusive date range and advising narrow queries, which signals that this operation can be expensive if not filtered. This is consistent with 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?

The description is two concise sentences. The first sentence states the action and resource, the second provides practical guidance. No filler or repetition; every sentence earns its place.

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 an output schema present, return values are covered elsewhere. The annotations carry the safety profile. The description adequately covers purpose and high-level invocation strategy for a tool with 18 parameters, though it could mention the default pageSize or the most commonly used filters.

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 input schema describes most parameters, with 72% coverage. The description itself adds little parameter-specific meaning—'inclusive date range' merely restates schema descriptions, and 'use filters' is generic. It does not compensate for the few undocumented parameters like agricultureDepartments or includeSubProject.

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 clearly states a specific verb ('Read') and resource ('posted account transactions') and even names the API endpoint (GET /AccountTransactions). This distinguishes it from sibling tools that deal with customers or general ledger 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?

The description offers clear usage guidance: use filters and small pages to keep accounting queries narrow. It does not explicitly name alternatives or exclusions, but no sibling tool overlaps with this functionality, so the absence of an explicit when-not-to-use is not a significant gap.

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