Get API usage

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not indicate whether the operation is read-only, idempotent, or has side effects. While it suggests a safe read (usage data), it fails to clarify permissions, rate limits, or data freshness, leaving significant gaps.

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 and is concise, but it lacks structure. It front-loads the purpose but omits details about parameters and output. It is not verbose, but it is under-specified given the need for parameter and behavior clarification.

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 that there is only one parameter and no output schema, the description should cover the rolling window mechanism, daily quota definition, and response format. It does not, leaving the agent unsure about the tool's full behavior and how to interpret results.

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 does not mention the 'windowHours' parameter. With 0% schema description coverage, the tool's purpose and the parameter's role are not explained. The schema provides min/max constraints but no semantic meaning. The description fails to compensate for this lack of parameter documentation.

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 identifies the tool as retrieving 'Your Clutter API usage (request counts by route)' and specifies the time window and quota. This distinguishes it from sibling tools that perform different actions (e.g., build, create, delete). The verb 'get' is implied, and the resource is explicitly stated.

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, such as other listing tools. There is no mention of prerequisites (e.g., authentication needed) or when not to use it. The description only states what it does, leaving the agent to infer any usage restrictions.

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