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

With no annotations the description carries the full load and does well: it discloses the auth scheme, that pages are metered per key per day (rate/quota behavior), and that a keyless call returns guidance rather than an error. It does not state whether the export ends at a known page count or whether ordering is stable, which a bulk-dump tool would benefit from.

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?

Three tight sentences, front-loaded with what the tool returns, followed by the access precondition and the keyless fallback. No filler; each clause adds information.

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 two-parameter, no-output-schema bulk export, the description covers scope, page size, auth, quota, and failure behavior. The main omission is the return shape and whether pagination terminates, which the agent must discover at runtime.

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 coverage is 0%, so the two parameters carry no documentation. The description compensates partially by stating '200 a page' (pageSize cap/default) but never explains the 'page' parameter's indexing or behavior. This is adequate but leaves real meaning unstated against a low-coverage schema.

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 (export) and resource (every entity of the Wen Receipts register), plus scope (the whole register, not a query) and pagination granularity. This clearly separates it from query-oriented siblings like entities_search and entity_lookup without needing to name them.

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 explicit preconditions (needs an access key via Authorization: Bearer) and the default page size, which frames when it's usable. It stops short of naming an alternative for filtered lookups (e.g. entities_search), so an agent must infer the when-not from the 'every entity' scope.

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