Export one bounded Micro data page

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds 'bounded' and 'live' context, which conveys pagination limits and current-data semantics beyond the annotations. It does not fully describe pagination behavior or ordering, but the annotation coverage lowers the burden.

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 a single front-loaded sentence with no filler. It efficiently communicates the action, resource types, and pagination nature. Every word contributes to the core meaning.

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 and annotations cover safety, so return details are not required in the description. However, the description omits practical usage context such as how path, limit, and offset interact, and it does not clarify when to choose this generic paging tool over resource-specific sibling tools. It is adequate but not complete.

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 low at 25%, and the tool description only enumerates the resource enum values, duplicating the schema enum. It gives no real guidance for path, limit, or offset beyond the word 'bounded' hinting at pagination. The description does not compensate enough for the underdocumented parameters.

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 states a clear action and resource scope: 'Read one bounded live page of project users, records, purchases, entitlements, products, files, or audit events.' It identifies the specific verb and the pagination behavior ('one bounded live page'), which distinguishes it from a full export tool. However, it does not explicitly differentiate it from sibling resource-specific tools like micro_users or micro_purchases.

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?

No guidance is given about when to use this tool versus alternatives such as micro_users, micro_records, or micro_export_manifest. The description implies a paging use case but provides no explicit when-to-use, when-not-to-use, or alternative routing. This is a significant gap given the large sibling tool set.

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