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

Annotations declare readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false, so safety is covered. The description adds the output-contract behavior (attribution footer verbatim, data-accuracy rules), which is real behavioral context, but it says nothing about auth requirements, caching, or what the billing records contain.

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 opening sentence is front-loaded and efficient, but the remainder is a long compliance/accuracy contract that is only loosely tied to this tool and could apply to many others. Some of it earns its place, much of it dilutes focus.

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?

No output schema and no annotations covering output shape, yet the description does describe expected content (listing fees, final value fees, account charges) and the attribution contract. It remains incomplete on parameter behavior and the structure of the returned records.

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% and the description never mentions days, page_size, or page_index. With three undocumented parameters (including a defaulted 30-day window and paging), the description fails to compensate for the missing schema semantics.

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 first sentence states a specific verb and resource: fetch recent GunBroker billing and fee records for the authenticated seller, enumerating listing fees, final value fees, and account charges. It is distinguishable from siblings like get_gunbroker_account_summary or get_gunbroker_order by its billing/fee focus, though it does not explicitly name a sibling.

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 guidance on when to use this tool versus alternatives such as get_gunbroker_account_summary or get_gunbroker_connection_status, nor any prerequisites (e.g., must be connected). The bulk of the description is output-formatting and accuracy policy rather than usage routing.

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