get_sales_report

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states it 'retrieves' a summary, implying a read operation, but does not mention any side effects, authentication requirements, rate limits, error handling, or what happens if event IDs are invalid. The behavior is minimal and not transparent.

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 extremely concise, consisting of two short lines. It front-loads the main action ('Retrieve sales report summary') and immediately provides key parameter details. No unnecessary words; every sentence earns its place. This is exemplary conciseness.

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 has an output schema (context indicates has output schema: true), so return values are presumably covered by the schema. The description covers the essential input parameters (event_ids, filter_by) but lacks usage guidance and behavioral transparency. For a simple retrieval tool, it is adequate but incomplete, leaving an agent uncertain about when to use it and what to expect beyond the 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?

With schema description coverage at 0%, the description must compensate. It does add meaning by specifying that event_ids are 'comma-separated' and that filter_by can be 'event' or 'date'. However, it does not fully explain the semantics of filter_by (e.g., what filtering by date means) or provide complete parameter documentation. It adds some value but leaves gaps.

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's purpose: 'Retrieve sales report summary for one or more event IDs'. It specifies the verb (Retrieve), resource (sales report summary), and the parameter scope (event IDs). However, it does not differentiate from sibling tools like get_attendees_report, so it lacks explicit sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives. The description mentions the filter_by parameter but does not explain when to choose this tool over other report tools, nor does it state any conditions or prerequisites for use. No exclusions or alternative recommendations are provided.

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