Get a funnel status

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

The description is extremely brief and does not disclose any behavioral traits beyond the fact that it's a GET request. Since no annotations are provided, the description should explain it's read-only, but it doesn't. It also doesn't mention authentication, error handling, or response behavior.

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 very short and efficient, but lacks substantive information. It is not overly verbose, but could be improved without adding length by including key details.

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?

The tool has no output schema, so the description should explain what is returned. It does not mention return type or structure. Given the complexity of a CRM funnel status, the description is incomplete.

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 description mentions the parameter only implicitly via the URL path ('{id}'), but does not explain the 'path' object parameter or what the id represents. With 0% schema coverage, the description adds minimal value beyond the parameter name.

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 'Get a funnel status' and includes the HTTP method and endpoint, making it easy to understand the action. It distinguishes from sibling tools like create, delete, update, and list all funnel statuses.

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 provides no guidance on when to use this tool versus alternatives like get_all_funnel_statuses. There is no context for prerequisites, use cases, or exclusions.

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