fiken_list_accounts

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered structurally. The description adds only that the account set can be narrowed, but discloses nothing about pagination behavior, default page size, or how results are ordered – moderate value over 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?

A single compact sentence, front-loaded with the verb and resource. Nothing wasted, though its brevity comes at the cost of substance rather than being a model of efficiency.

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 5-parameter, list-style tool with 0% schema coverage and no output schema, the description omits the pagination model and the meaning of the account-range parameters. An agent would have to guess at how from_account/to_account behave and how to page through results.

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 0% with 5 parameters, so the description must compensate and largely does not. 'Optional account restrictions' vaguely gestures at from_account/to_account but never explains range semantics, inclusivity, or format, and says nothing about page, page_size, or company_slug.

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 clear verb+resource: list accounts in the chart of accounts, with optional account restrictions. An agent knows what it retrieves. It does not, however, distinguish this from the sibling fiken_list_account_balances (balances vs. master data), which is a meaningful ambiguity in an accounting context.

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?

There is no statement of when to use this versus fiken_list_account_balances or fiken_list_account_balances-style siblings, and no prerequisites such as needing a company_slug resolved first. The only usage hint is the implicit 'optional restrictions' phrase, which is not guidance about tool selection.

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