get_target_account_funnel

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

No annotations provided; description discloses the scoring formula, behavior of intent_spiking, and required mode. Does not mention side effects or read-only nature, but sufficiently transparent for a read-like operation.

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?

Three sentences front-loaded with purpose, then scoring formula, then a usage tip. No wasted words, efficiently 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?

No output schema or annotations; description provides scoring algorithm and a requirement but lacks details on response format and parameter semantics, making it minimally adequate.

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 0% schema description coverage, the description only explains intent_spiking; other parameters (limit, account_tier, min_sessions_30d, etc.) are not described, leaving agents to infer meaning from names and enums alone.

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 returns ranked target accounts from the dark funnel sorted by a composite priority score, distinguishing it from sibling tools like get_target_account_activity.

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?

Provides explicit prerequisites (BigQuery mode, completed enrichment run) and a tip on using intent_spiking. Lacks explicit when-not-to-use or alternatives, but overall guides appropriate usage.

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