billing_history

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions that the wallet is resolved to its organization over SIWX and that a wallet not linked requires an admin key, which is useful. However, it does not disclose whether the operation is read-only (implied by 'View'), whether results are paginated (despite the 'limit' parameter suggesting pagination), or what the response structure contains.

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 two sentences, front-loaded with the purpose in the first sentence. The second sentence adds essential behavioral context without waste. Every part earns its place, making it highly concise and structured.

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 simple tool with no output schema, the description covers purpose and key behavioral context (resolution, admin key). However, it omits details about the returned data structure (e.g., what fields are in the billing history) and does not mention that results may be paginated despite the 'limit' parameter. Given the simplicity, it is adequate but not fully 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?

The input schema covers both parameters with descriptions, achieving 100% coverage. The tool's description does not add new semantic meaning beyond the schema; it only provides context about wallet resolution. Per guidelines, baseline is 3 when schema coverage is high, so this score is appropriate.

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 clearly states 'View billing ledger history' with the specific resource 'agent's allowance wallet'. This gives a clear verb and resource. However, it does not explicitly differentiate from similar sibling tools like 'allowance_status' or 'check_balance', which could lead to confusion about when to use this tool over others.

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 provides some usage context, such as wallet resolution over SIWX and the need for an admin key if the wallet is not linked. However, it lacks explicit guidance on when to use this tool versus alternatives like 'allowance_status' or 'get_usage'. No alternatives are named, leaving the agent to infer the correct usage scenario.

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