Get all funnel statuses

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

The description implies a read-only GET operation but does not disclose behavioral details (e.g., whether it returns paginated results, ordering, or error handling). Without annotations, this is minimal but acceptable for a simple list endpoint.

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 but includes the HTTP method, path, and a brief purpose. It could be improved with structured sections (e.g., usage notes).

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 the simplicity of the operation, the description covers the basic purpose. However, it lacks details about the response format, pagination, or authentication, which would be helpful for a complete understanding.

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?

No parameter description beyond the schema. The funnelId parameter is not explained (e.g., format, required, or how to obtain it). Schema coverage is 0%, so the description adds no value here.

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 HTTP method, resource path, and action: 'Get all funnel statuses'. It explicitly requires a funnelId and is distinct from sibling tool 'weeek_get_a_funnel_status' which gets a single status.

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?

No explicit usage context or alternatives are provided. The description does not mention when to use this tool versus alternatives like the single-status version.

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