or_activity

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

The description claims 'grouped by endpoint' but the input schema's aggregate enum does not include any endpoint grouping, with 'none' as the default representing raw rows. This contradiction makes the description misleading. It also fails to clarify how the 'date' filter interacts with the fixed 30-day window and does not disclose default limits or output behavior.

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 short and front-loaded, but its brevity comes at the cost of omitting essential information and introduces an inaccuracy. The sentence about filters partially earns its place but is incomplete.

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 five optional parameters and no output schema, the description should explain defaults, aggregation behavior, and result format. It only covers a subset of filters and does not mention the 'limit' or 'aggregate' parameters, making it incomplete for a tool this complex.

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?

Although schema description coverage is 100%, the description only lists three of the five parameters and omits 'limit' and 'aggregate'—the latter being critical to the stated grouping behavior. It adds no new meaning beyond the schema and partially contradicts the schema's aggregation options.

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 states the tool shows OpenRouter usage grouped by endpoint for the last 30 UTC days, using the verb 'Show' and specifying the resource and scope. This distinguishes it from sibling tools like or_overview and or_generation, which likely cover different aspects.

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 implies usage for viewing recent activity but provides no explicit guidance on when to use this tool instead of siblings or any exclusions. It mentions optional filters but does not explain their mutually exclusive or complementary nature.

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