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

No annotations are present, so the description carries the full burden. It discloses public access, UTC day boundaries, zero-fill behavior while off, and aggregate-only semantics. It does not mention rate limits or response formatting, but the most important behavioral traits are covered.

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?

One dense sentence front-loads the purpose and packs the metric list, date behavior, and aggregate-only caveat without wasted words. Every element earns its place.

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?

With no output schema and no annotations, the description enumerates all returned metrics and the row cadence, which is sufficient for a simple aggregate query. It stops short of specifying exact JSON field names and ordering, but the core usage context is complete.

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 0%, so the description must compensate. It explains that `days` controls the number of UTC daily rows and restates the default and maximum, adding the crucial UTC-per-day interpretation. The single parameter is semantically well covered.

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 a public aggregate daily pulse endpoint, enumerates the included metrics, and distinguishes itself with 'Aggregates only' from granular sibling tools like get_meter_receipt or list_posts. The resource and scope are immediately recognizable.

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?

The 'Aggregates only' phrase implies the tool is for summary-level data rather than granular records, but it never explicitly names alternatives or states when to use this tool versus siblings like get_meter, get_feedback_stats, or list_posts. The usage context is implied, not explicit.

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