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

No annotations are provided, so the description carries the full burden of disclosing behavior. It says 'Return', which hints at a read-only operation, but it does not describe data freshness, time window, output format, permissions, or any side effects. For a tool without annotations, this is a minimal behavioral disclosure.

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 sentence that front-loads the verb 'Return' and resource 'aggregate machine-sales funnel', then efficiently lists the six key metric categories. Every word contributes, and there is no fluff or repetition.

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?

While the description clearly lists the metrics, it omits the return structure, time window, units for USDC revenue, and any caveats such as lack of filtering. With no output schema and no annotations, an agent lacks some information about the exact response shape and scope. It is adequate for a simple aggregate telemetry tool but leaves notable contextual gaps.

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 tool has zero parameters and schema description coverage is 100%. With no parameters, the description does not need to explain any inputs. The list of metrics is about return values, not parameter semantics. The no-parameter baseline of 4 applies.

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 has a specific verb 'Return' and a clear resource: the aggregate machine-sales funnel. It enumerates the exact metrics returned (requests, quotes, paywalls, paid requests, unique payers, USDC revenue), making it distinguishable from the quoting-focused sibling tools such as machine_quote and quote, which are about generating individual quotes rather than aggregate metrics.

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 aggregate nature of the tool implies it is used for high-l-level sales funnel metrics rather than for quoting tasks, but the description provides no explicit when-to-use or when-not-to-use guidance, and does not name any sibling tools or alternative conditions. Usage is only implied, not directly stated.

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