get-excel-table

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Read-only' which is consistent but does not disclose additional behaviors like rate limits or dependencies beyond what annotations provide.

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 and contains a helpful tip, but the first sentence is vague ('Represents a collection of tables'). It could be more front-loaded with 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?

With no output schema, the description partially explains return values (table properties) but omits mention of ID, name, or the purpose of orthogonal parameters like select and expand. The tool's complexity is not fully supported.

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 coverage is 100%, so each parameter has a description. The tool description adds a tip about returned properties (columns, showHeaders) but does not elaborate on parameters like select, expand, or fetchAllPages beyond the 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 tool retrieves a specific table by name or ID and lists returned properties (columns, showHeaders, etc.), distinguishing it from sibling tools like list-excel-tables or get-excel-range.

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?

While the tip implies use for getting a specific table, there is no explicit guidance on when to use this versus list-excel-tables or how to handle pagination; the context is implicit rather than directive.

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