get_account_records

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral detail beyond them: deletion markers are excluded, flight categories are restricted to this account, and token/secret/receipt fields are redacted. These are exactly the caveats an agent needs before trusting returned data, and 'no outgoing account changes are sent' reinforces the safe-read profile without contradicting it.

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?

Four short lines, all doing work, with the core action front-loaded and the caveats and limit following. The category list is slightly padded by 'etc.', but there is no filler or repetition.

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?

An output schema exists so return shape needn't be described, and the description still covers the redaction policy, category discovery, and limit bounds. The remaining gap is the semantics of offset and refresh, which leaves an agent guessing about pagination and cache-bypass behavior.

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%, so the description must carry parameter meaning; it covers 'kind' via the category enumeration plus the get_schema pointer and bounds 'limit' to 1..200, but says nothing about 'offset' or 'refresh'. With two of four parameters still opaque, the compensation is real but incomplete.

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 ('Read') and resource ('a sync category') and enumerates the categories (tickets, notes, subscriptions, profile, friends, favorites, settings), which clearly separates it from flight-specific siblings like get_flight or list_flights. It falls short of a 5 only because it doesn't explicitly name which sibling to use instead for overlapping data.

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 concrete onboarding guidance by telling the agent to discover category names via get_schema('SyncResponseData'), which is the key prerequisite for calling it. It also states the 1..200 limit. It does not state when-not to use this tool or name a direct alternative for account-scoped data, so it stays below 5.

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