Get Funnel Stages

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

Annotations declare readOnlyHint=true, and the description does not contradict this. It adds examples of common stage names, which provides context beyond the annotation, but does not disclose pagination behavior or any potential side effects. Overall, it offers a modest addition to the annotation.

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, efficient sentence that front-loads the primary purpose. All words are necessary, and there is no repetition. It is appropriately brief while being informative.

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?

Despite full schema coverage and readOnlyHint, the description does not describe the response format (e.g., whether it returns a list of objects with IDs and names) or clarify the pagination behavior indicated by the parameters. This leaves the agent without crucial information for processing results. The description should compensate for the missing output schema.

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 each parameter described in detail. The description adds no extra meaning to the parameters (name filter, pagination IDs, page size). With high coverage, the baseline of 3 is appropriate.

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 verb 'Get' and the resource 'all lead funnel stages' with concrete examples (MQL, SQL, Opportunity, Customer). It is unambiguous and distinguishes itself from sibling tools, none of which retrieve funnel stages.

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 description gives the context of retrieving configured stages but lacks explicit guidance on when to use this tool versus alternatives, or when not to use it. Since no sibling tool retrieves stages, the omission is minor, but the dimension expects some usage direction.

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