add_shape

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

With no annotations, the description carries full burden. It only states what the tool does without disclosing side effects, error behavior, idempotency, permissions, or return values. Minimal behavioral transparency beyond the core action.

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 a single, clear sentence (15 words) with no redundancy. It efficiently conveys the essential action and key parameters without extraneous information.

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's complexity (8 parameters, no output schema), the description lacks critical context. It omits details like coordinate system, 1-based slide index, the 'role' parameter, and expected return value. Incomplete for an agent to fully understand usage implications.

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 baseline is 3. The description adds 'optional fill colour' which echoes the fillColor parameter description. It does not add new semantic meaning beyond summarizing the schema's already documented parameters.

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 uses a specific verb 'adds' and identifies the resource 'shape to a slide'. It mentions key parameters (type, position, size, optional fill colour), distinguishing it from sibling tools like update_shape and delete_shape.

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 implies usage when adding a shape to a slide but provides no explicit guidance on when to use this tool versus alternatives (e.g., add_image, add_text_item) or prerequisites (e.g., slide existence). No when-not-to-use or context-specific advice.

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