transactions_aggregate_by_hosting

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

Discloses the silently ignored productId behavior, provides HAL template and spec link. Annotations already indicate safe read-only operation; description adds valuable context.

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?

Concise with front-loaded purpose. Includes spec link and note, but no wasted words. Slightly dense but acceptable.

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?

No output schema, but description explains alias nature and behavior. Lacks any hint about return format. Adequate but not 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 coverage is only 33% (only aggregation described). The description does not elaborate on startDate/endDate parameters. Limited added value beyond schema.

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 it's a friendly alias for transactions_aggregate_by_metric with metric='hosting'. Distinguishes from sibling by noting the productId behavior.

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 advises when to use the sibling instead (when productId scoping is needed) and documents that productId is silently ignored here.

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