github_billing_get_github_billing_usage_report_user

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

No annotations are provided, so the description must fully convey behavioral traits. It implies a read-only operation ('Get') but does not explicitly confirm idempotency, data scope, permissions, or side effects. The description adds no behavioral context beyond the basic operation.

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 sentence that is front-loaded with the core purpose. It is concise and avoids unnecessary words. However, it could benefit from a brief clarification about the report's content or usage context without becoming verbose.

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?

There is no output schema, and the description does not explain what data the report contains, its format, or any filtering behavior beyond the parameters. The tool likely returns a billing report, but the agent has insufficient information to interpret the results. Given the complexity of billing data, the description is incomplete.

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% coverage with detailed parameter descriptions for year, month, and day, and username is described as 'username'. The tool description does not add any additional parameter semantics beyond what the schema already provides. Baseline 3 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 'Get billing usage report for a user' clearly states the action (get) and resource (billing usage report for a user). It distinguishes from the org variant by specifying 'user', but does not differentiate from the summary report version, which is a sibling tool. The verb and resource are specific enough for basic understanding.

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 no guidance on when to use this tool versus alternatives like the summary report or org-level report. Given the large number of sibling billing tools, the agent lacks context to choose correctly. No exclusions or prerequisites are mentioned.

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