excel_create

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

The description does not disclose key behavioral details such as file location, naming convention, overwrite behavior, or return value. With no annotations, the agent must infer critical traits, risking incorrect usage.

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, focused sentence with no extraneous words. It is front-loaded and efficiently conveys the core action.

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 no output schema and no parameters, the description should clarify what the tool returns and any side effects. It fails to do so, leaving the agent with significant ambiguity about how to use the result or verify success.

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 input schema has zero parameters, so schema coverage is 100% by default. However, the description offers no insight into default behavior (e.g., file name, save location), leaving the agent uncertain about what the tool will do. A baseline 3 is appropriate given the empty schema.

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 the action (create) and resource (new Excel spreadsheet), making the purpose immediately understandable. It implicitly distinguishes from sibling tools like excel_read and excel_write_cell by focusing on creation, but lacks explicit differentiation.

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 vs. alternatives. The description does not mention context, prerequisites, or when to avoid it, leaving the agent without decision support.

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