create_workbook

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

No annotations exist, so the description must carry the full burden. It does not disclose whether the tool overwrites existing files, requires specific permissions, or has side effects like saving to disk. The note about session_id hints at session association but lacks clarity.

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 concise with two sentences for purpose and two lines for parameters. It is front-loaded with the core purpose, but could be more structured (e.g., separate usage and notes sections). Still, no redundancy.

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 simplicity and the presence of an output schema, the description is partially complete. It lacks details on error conditions, prerequisites (e.g., need for an open session), and what the output contains. For a creation tool, this is a moderate gap.

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 0% schema description coverage, the description adds meaningful context: session_id is for existing sessions, filepath is deprecated. This goes beyond mere type information, though more detail (e.g., format of session_id) would be helpful.

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 'Create new Excel workbook' clearly states the verb and resource, distinguishing it from siblings like open_workbook (opens existing) and create_worksheet (creates sheet within workbook).

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 provides almost no guidance on when to use this tool versus alternatives. It mentions a deprecation note for filepath and recommends session_id, but does not discuss selection criteria among sibling tools.

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