get-excel-range

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

The description contradicts the 'readOnlyHint: true' annotation by using 'invoke', which suggests a potential mutation. The description does not add any useful behavioral context beyond the annotations and may mislead the agent.

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 extremely short (four words) but under-specified. While concise, it fails to convey essential information and is closer to a placeholder than a useful description.

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 should explain the return format or behavior. It does not mention that the tool retrieves cell values, formulas, or metadata. For a tool with 7 parameters, this description is critically incomplete.

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 100% description coverage, so the baseline is 3. The description adds no parameter-level information, but the schema already documents each parameter. Thus, no additional value is provided.

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 'Invoke function range' is vague and misleading. It does not clearly state that the tool retrieves an Excel range; 'invoke' implies calling a function, which may be interpreted as an execution rather than a read operation. It fails to differentiate from sibling tools like 'get-excel-table' or 'get-excel-used-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?

The description provides no guidance on when to use this tool versus alternatives. Sibling tools exist for similar purposes (e.g., 'get-excel-used-range'), but no comparison or context is given.

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