show_viewdetails

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

The description implies a read operation ('Get view dimension layout') and provides a link to dependent tools, but does not explicitly state read-only or disclose any behavioral traits like authorization requirements or side effects. With no annotations, the description carries the full burden and barely meets the minimum.

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?

Two sentences with no wasted words. The first sentence conveys the core action, and the second provides essential follow-up context about how the output is used. Highly efficient.

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 explains the purpose and its role in a workflow, but does not describe the output structure or any prerequisites (beyond the parameters). With four required parameters and no output schema, the description could be more complete regarding what the user receives.

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 description coverage is 100%, so each parameter already has a description. The tool description does not add additional meaning beyond the schema, resulting in a baseline score of 3.

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 view dimension layout (rows, columns, pages) and explicitly links to sibling tools (write_cells, show_viewdimensionitems) by stating the IDs are needed for them, effectively distinguishing its purpose.

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?

Explicitly mentions that dimension IDs from this tool are prerequisites for write_cells and show_viewdimensionitems, providing clear context for when to use this tool. However, it does not discuss when not to use it or mention alternative tools.

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