createInnovationFunnelSlide

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

The description mentions 'create or update', implying mutability based on the '_index' parameter, but does not disclose side effects, error conditions, or what constitutes an update vs. creation. The schema provides some behavioral cues (e.g., default append behavior), but the description adds minimal transparency beyond that.

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 extremely concise at 6 words, which is front-loaded with the action. However, it is arguably too terse, omitting necessary context that could be added without much length.

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 tool has 3 parameters (one required) and no output schema, the description is incomplete. It does not clarify what a 'placeholder' is, how 'counts' relates to 'stages', or what the tool returns. For a tool with many siblings, more context is needed for correct invocation.

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?

With only 33% schema description coverage, the description should compensate but does not. It fails to explain the meaning of 'stages' or 'counts', leaving the agent to infer from names alone. The '_index' parameter is the only one described in the schema, and the description adds nothing to aid understanding.

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 tool creates or updates an innovation funnel placeholder, specifying both the verb and resource. However, it does not differentiate from sibling tools like 'createFunnelSlide' or 'createPipelineFunnelSlide'.

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 guidance is provided on when to use this tool versus alternatives (e.g., other funnel slides) or any usage context. The description lacks any when-to-use or when-not-to-use information.

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