get_client_info

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

No annotations provided. The description claims it returns a billable usage report but contradicts the tool name. It mentions date range functionality that isn't supported by the input schema, creating confusion about behavior.

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?

Only two sentences, but they are misleading and lack clarity. The phrase 'If not provided' is ambiguous and does not correspond to any parameter, making the description inaccurate rather than concise.

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 name vs. description mismatch, missing date range parameter, and lack of behavioral disclosure, the description fails to provide sufficient context for a tool with one required parameter and an output schema.

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 description fails to explain the sole parameter 'client_id'. It mentions 'specified date range' but no such parameter exists, directly contradicting the schema. With 0% schema description coverage, the description provides no meaningful parameter guidance.

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 name 'get_client_info' suggests retrieving general client information, but the description says 'Get billable usage report for specified date range,' which is a mismatch. The sibling tool 'get_billable_usage' likely handles billable usage, causing confusion about this tool's role.

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 explicit guidance on when to use this tool vs. alternatives like 'get_billable_usage'. The description implies a default date range but is vague, leaving the agent unsure of the intended use.

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