excel_add_worksheet

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

With no annotations, the description carries full burden but fails to disclose any behavioral traits (e.g., whether the operation is read-only or destructive, permissions needed, etc.). It does not even confirm that the tool creates a new worksheet.

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 short but front-loads irrelevant routing info (JWT, tenant, company scope) instead of the tool's actual functionality. While concise, it wastes space on non-essential details.

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 lack of annotations and the presence of an output schema (not detailed), the description should clarify the tool's operation and expected output. It completely fails to do so, leaving the agent without sufficient context.

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?

The schema coverage is 0% for the single parameter 'arguments'. The description only says it is a 'JSON string of arguments for the connector operation' without detailing the expected structure or keys, adding minimal value.

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 states 'Excel connector operation `add_worksheet`' which hints at adding a worksheet but does not explicitly state the tool's purpose. It focuses on routing details rather than the core function, leaving the agent unclear about what the tool does.

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 sibling tools like `excel_list_worksheets` or `excel_update_range`. The description lacks any context for appropriate usage.

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