table_to_excel

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

No annotations are provided. The description discloses that it reads input and writes .xlsx within PathGuard allowed roots, and requires overwrite=true for existing files. This adds behavioral context beyond the schema, though it does not mention potential failures or performance characteristics.

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 two concise sentences. The first sentence states the core functionality and the second adds usage context and a key constraint. No redundant information, perfectly front-loaded.

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?

The description covers the essential purpose, usage, and constraints. An output schema exists, so lack of return value explanation is acceptable. It is missing details on error conditions or support for older .xls format, but for a simple export tool it is largely complete.

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 already provides detailed descriptions for each parameter (table, out_xlsx, overwrite). The tool description echoes key constraints ('PathGuard allowed roots', 'overwrite=true') but adds no new meaning beyond the schema. Given the high schema coverage, baseline 3 is appropriate.

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 'Export an attribute table or feature class table to an Excel workbook' using a specific tool. It specifies the action (export), resource (table/feature class), and output format (Excel). This distinguishes it from siblings like excel_to_table, feature_to_csv, and export_to_geojson.

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 says 'Use this to share tabular GIS attributes with analysts, reports, or spreadsheet workflows,' giving clear usage context. However, it does not explicitly mention when not to use it or compare with alternatives like csv export, so guidance is slightly implicit.

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