getRawMetricLogs

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

No annotations provided, so description carries full burden. Describes endpoint's behavioral constraints (no filters, pagination, ordering, aggregation). Does not mention authorization, rate limits, or maximum return size, but the explicit limitations are valuable.

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?

Two concise sentences. First sentence states core purpose. Second sentence adds limitations and alternative. No superfluous words.

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?

No output schema provided. Description lacks details on return format (fields, row count, ordering). While limitations are covered, the output structure is important for a retrieval tool. Missing this information reduces completeness.

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%: both parameters have descriptions. The tool description does not add significant meaning beyond the schema, such as expected format or constraints. Baseline score of 3 is appropriate when schema sufficiently documents parameters.

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 verb 'Get', resource 'Usage Event rows', qualifiers 'recent' and 'by ID'. Distinguishes from siblings like getAggregateLogs and listRawMetrics by specifying resource type and ID-based retrieval.

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?

Explicitly states limitations: no filters, pagination, ordering, or aggregation. Directs users to aggregate endpoints for filtered/aggregated queries. Provides clear when-to-use and when-not-to-use guidance.

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