vexo_overview

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

Describes scanning all events in date window (<=31 days), returning totals and top breakdowns, and the return shape including cap at 15 per top list and failure mode. Adds behavioral details beyond annotations (readOnlyHint, openWorldHint).

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 paragraphs with purposeful sentences. Front-loaded with purpose and usage. No fluff, every sentence adds value.

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?

Fully explains purpose, behavior, parameter constraints, return shape, and failure mode. No gaps given the tool's simplicity and lack of output schema.

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?

Input schema parameters have 0% description coverage, but description explains they are ISO dates, end inclusive, and max 31 days apart. This adds essential semantic meaning.

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?

Clearly states 'High-level breakdown of activity in a date window' and 'Good first call to understand an app's traffic', specifying verb (overview) and resource (activity in date window). Distinguishes from siblings like vexo_count_events and vexo_event_timeline.

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 recommends as a first call for understanding traffic. Implicitly suggests when not to use (e.g., for detailed event counts or timelines, use other tools). No explicit exclusions, but context is clear.

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