kaiten_chart_sales_funnel

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly communicates that the call is asynchronous, returns a compute_job_id, and requires polling via kaiten_get_compute_job. This is a critical behavioral trait beyond what the schema states, though it omits error/permission 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?

Three sentences, each purposeful: purpose, prerequisites, and async handling. Information is front-loaded and there is no filler or repetition of schema 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?

Given no output schema and no annotations, the description supplies the necessary workflow (compute_job_id + polling), the key board_configs prerequisites, and enough framing to choose the tool. It doesn't detail every param, but the schema already describes those; the missing result-shape detail is delegated to kaiten_get_compute_job.

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%, so the baseline is 3. The description adds value by constraining board_configs: columns must be marked 'won' or 'lost' and each enabled board needs a sum property in settings. This explains requirements the schema only partially encodes.

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 opens with 'Build a Sales Funnel Chart for a space', naming a specific verb, resource, and scope. This uniquely identifies the tool among the many kaiten_chart_* siblings and is clear without requiring the schema.

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 clear operational context: board_configs must reference enabled boards, won/lost columns, and a configured sum property. It also states the async workflow and names kaiten_get_compute_job for polling. It does not explicitly compare with alternative chart tools, so it falls short of a 5.

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