Lead Journey

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

Annotations provide readOnlyHint=true, and the description complements this by detailing the included data (sales, calls, carts, ad attribution). No contradictions. Adds behavioral context beyond annotations, though no mention of rate limits or authentication.

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 sentences: first states purpose and scope, second provides usage guidance. No unnecessary words, information-dense and well-structured.

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?

Given no output schema, the description effectively hints at return structure (includes sales, calls, carts, ad attribution). For a single-parameter tool with clear annotations and schema, this is sufficient. Could be more precise but still 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?

The schema specifies a single required 'ids' parameter; the description adds that IDs should be comma-separated and obtained from hyros_get_leads first. This significantly aids correct invocation despite 100% schema description coverage.

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 retrieves the complete customer journey for one or more leads, including sales, calls, carts, and ad attribution sources. This distinguishes it from siblings like hyros_get_leads (which lists leads) and hyros_get_sales (which retrieves sales only).

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 says 'Use this to understand what ads drove a customer to convert', providing clear usage context. However, it does not mention when to avoid using it or offer alternatives, stopping just short of a 5.

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