get_workbook_info

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

With no annotations, the description must disclose behavioral traits. It only states what information is returned, not whether the operation is read-only, safe, or requires special permissions. There is no mention of side effects or mutations, but given the nature, it's likely safe. However, the description omits explicit behavioral transparency.

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 concise and front-loaded, using a single sentence to convey exactly what information the tool returns. No wasted words.

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 tells what the tool outputs but fails to explain the input parameter or confirm the operation's behavior (e.g., read-only). With no output schema, describing the output format would be helpful. For a simple tool, it is minimally adequate but has clear gaps.

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 a single required parameter 'session_id' with no description. The tool description does not mention this parameter or explain how to obtain it or what it represents. With 0% schema description coverage, the description fails to add any semantic context for the parameter.

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 identifies the tool's purpose: retrieving workbook-level information including sheet names and their used-range dimensions. The verb 'Get' and resource 'workbook details' are specific, and the output is well-defined. However, it does not explicitly differentiate from siblings like 'list_sheets' or 'get_used_range' in the description, though the combination is unique.

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 over siblings. It doesn't mention that for individual sheet details one might use 'get_used_range' or 'list_sheets', or that this tool provides aggregated info. Usage context is implied but not explicit.

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