createChangeCurveSlide

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

With no annotations, the description should explain behavioral traits. It only says 'create or update' but does not disclose that update behavior depends on the _index parameter, nor does it mention any side effects, error states, or constraints.

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?

While very short, the description fails to be informative. Conciseness here sacrifices necessary detail, making it insufficient for proper tool use.

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 complexity (3 parameters, optional update, required array with minItems), the description is incomplete. It does not explain return values, the update mechanism, or provide any background on change curves.

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 low (33%) yet the description adds no meaning to the parameters. It mentions 'stages' but does not define what a stage is or the expected format. The _index parameter has a helpful description in the schema, but the description does not leverage or reinforce it.

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 it creates or updates a change curve with stages, identifying the specific resource (change curve slide). However, it does not differentiate this tool from numerous other create*Slide siblings, which all have similar patterns.

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 slide creation tools). No prerequisites, exclusions, or context for choosing this tool are mentioned.

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