listRawMetrics

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

No annotations are provided, so the description bears full responsibility. It does not disclose pagination behavior (cursor, limit), ordering, or authentication needs. The presence of internal parameter '__userContext' is not explained. The description is too brief to provide adequate behavioral transparency.

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 consists of two short, front-loaded sentences. Every word is necessary; it states the purpose and key capability without fluff.

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 complexity (10 parameters, no output schema, no annotations), the description is insufficient. It does not explain pagination, sorting, or how filtering works. The internal '__userContext' parameter is not acknowledged. The description lacks completeness for a list tool.

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?

Schema description coverage is 100%, so each parameter has its own description. The tool description adds only a summary statement about filters (ID, name, API slug) which does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate as the description adds marginal value.

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?

Description clearly states 'List Usage Events' which indicates the verb (list) and resource (usage events). The tool name 'listRawMetrics' and sibling tools like 'getRawMetricById' suggest it lists multiple raw metrics, so purpose is clear. However, it does not explicitly differentiate from similar list or get tools, lacking explicit sibling differentiation.

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 on when to use this tool versus alternatives such as 'getRawMetricById' for single retrieval. No mention of prerequisites, pagination, or when not to use. The description only states supported filters but does not provide usage context.

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