Read a Rootr spreadsheet

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by explaining the returned data structure (sheets with sparse cells map and dimensions), which is valuable beyond the annotations.

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 at two sentences, with no wasted words. The first sentence defines the core functionality, and the second provides immediate context on when to use it. 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?

Given the tool's simplicity (one parameter, no output schema), the description adequately explains the purpose, input, and output shape (sheets with sparse cells and dimensions). It lacks details on the cells map structure, but for a read tool with good annotations, this is sufficient.

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?

With 100% schema coverage and only one parameter ('spreadsheetId' described as 'SPREADSHEET node id'), the description adds no additional meaning. The baseline of 3 is appropriate as the schema already fully documents 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 states 'Read a Rootr SPREADSHEET node' with specific verb and resource. It mentions the output structure (sheets with sparse cells map and dimensions), distinguishing it from sibling tools by noting it should be called before update/patch operations.

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 explicitly advises when to call this tool ('before rootr_update_spreadsheet / rootr_patch_spreadsheet_cells'), providing clear usage context. However, it does not mention when not to use it or offer explicit alternatives for different tasks, missing the highest tier.

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