get_stats

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves stats, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits (beyond mentioning it as a stat), error handling, or response format. This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that lists all key stats without unnecessary words. It is front-loaded with the verb 'Get' and directly enumerates the resources, making it easy to parse and understand quickly.

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 has 0 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It states what stats are retrieved but lacks details on response format, error cases, or usage context. For a simple stats retrieval tool, this is acceptable but leaves room for improvement in behavioral transparency.

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 tool has 0 parameters, and the input schema has 100% coverage (empty object). The description doesn't need to add parameter details, so it appropriately focuses on the tool's purpose. A baseline score of 4 is given as it compensates for the lack of parameters by clearly stating what stats are retrieved.

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 the tool's purpose: retrieving statistics including credits left, transcripts created, plan, and rate limit. It uses a specific verb ('Get') and lists the resources, though it doesn't explicitly differentiate from sibling tools like 'get_transcript' or 'list_transcripts' beyond the type of data returned.

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 provided on when to use this tool versus alternatives. The description lists what stats are retrieved but doesn't mention context, prerequisites, or comparisons to sibling tools like 'list_transcripts' for transcript-related queries or 'get_transcript' for individual transcript details.

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