create_chart

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'create chart' without mentioning side effects (e.g., overwriting existing charts), permission needs, or error states. This is insufficient for a creation tool.

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 succinct with a clear first sentence followed by a parameter list. No unnecessary information. It could be more structured (e.g., grouping optional params), but it's acceptably concise.

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 9 parameters and the presence of an output schema, the description is incomplete. It does not explain return values, prerequisites (e.g., workbook must be open), or error handling. The output schema exists but is unmentioned.

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 description coverage is 0%, so the description adds meaning by labeling each parameter (e.g., 'Name of worksheet'). However, the descriptions are very brief and lack validation details, types, or examples. Baseline 3 due to low coverage.

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 'Create chart in worksheet' with a verb and resource. It distinguishes from siblings (no other chart creation tool) and lists parameters. However, it does not elaborate on different chart types or variations.

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 advises using session_id for better performance and notes filepath is deprecated. However, it provides no guidance on when to choose this tool over other tools (e.g., create_pivot_table, create_table) or context for chart creation.

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