get_funnel

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

No annotations provided, so description carries full burden. Explains what data returns (conversion at each stage) which is valuable behavioral context. However, omits read-only safety confirmation, error conditions (e.g., invalid agentId), or rate limiting details.

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?

Single efficient sentence with critical parenthetical stage enumeration. Front-loaded with core action ('Get the prospect funnel'). No redundant words or repetition of schema elements. Every clause earns its place by conveying funnel-specific information.

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?

Adequate for a 2-parameter read operation without output schema. Describes return value conceptually (conversion stages). Could improve by mentioning error handling (e.g., agent not found) or data freshness, but satisfies requirements for this complexity level.

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 100% with complete descriptions for agentId and platform. Description mentions 'for an agent' which loosely maps to agentId parameter, but adds no syntax details, format examples, or semantic constraints beyond what schema already provides. Baseline score appropriate for high-coverage schemas.

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?

Description uses specific verb 'Get' with specific resource 'prospect funnel' and distinguishes from siblings by detailing unique conversion stages (discovered → contacted → engaged → replied → converted). Clearly differentiates from generic 'get_agent_stats' or 'get_dashboard' siblings.

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?

Implies usage context (analyzing conversion pipeline for a specific agent) but lacks explicit guidance on when to choose this over 'get_agent_stats' or 'get_activity'. No explicit alternatives or exclusions mentioned.

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