Inspect Micro purchases

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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond annotations: the ledger is 'latest', 'bounded', and 'normalized', and the tool explicitly avoids exposing payment credentials or card data. This gives an agent useful privacy and scope expectations.

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, tightly written sentence with no filler. It front-loads the action and resource, then adds the key privacy qualifier. Every part earns its place.

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?

Given the tool's simplicity, one optional parameter, rich annotations, and an output schema, the description is largely complete for an agent to invoke correctly. The only minor gap is lack of explicit guidance on choosing among related financial inspection siblings, but that is not critical for basic invocation.

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?

The input schema has 100% description coverage for the single optional 'path' parameter, including its default behavior. The description does not elaborate on the parameter, but since the schema already documents it fully, the baseline score of 3 applies.

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 specific verb ('Read'), a specific resource ('bounded normalized purchase ledger'), and a clear scope ('linked owner project'). It also adds a meaningful differentiator by noting that payment credentials and card data are not exposed, which helps distinguish it from broader billing or financial tools.

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?

The description implies usage context by positioning this as a read-only inspection of purchase ledger data, but it does not explicitly state when to use this tool versus related siblings like micro_billing, micro_plans, or micro_usage. No exclusions or alternative routing are provided.

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