Get Activity Metrics

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

Annotations already provide readOnly, openWorld, and idempotent hints. The description adds the default-to-today-UTC behavior and clarifies that it returns combined metrics, which is extra context beyond the annotations. No contradiction with annotations.

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, front-loaded sentence that conveys the action, resource, and default behavior without any redundant or filler words. Every part 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?

The tool is simple with rich annotations and complete schema coverage. The description adequately conveys the core purpose and default date behavior. The only gap is that no output schema exists and the return format is not explicitly described, but for a simple metrics query this is acceptable.

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 schema fully describes the single 'date' parameter with ISO 8601 format and default value, giving 100% coverage. The description only repeats the default behavior, adding no additional parameter-level meaning beyond what the schema already provides.

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 uses a specific verb 'Get' with a specific resource 'combined DAU/MAU activity metrics' and a date specifier. It clearly distinguishes itself from sibling tools like lyzr_get_dau and lyzr_get_mau by emphasizing 'combined'.

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 description provides useful context by stating the date defaults to today UTC, but gives no explicit guidance on when to use this tool versus alternatives such as get_dau or get_mau. The intended usage is implied rather than clearly stated.

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