get_sheet_content

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

No annotations are provided, so the description carries the full burden. It only states 'context control optional' but does not disclose behavioral traits like data volume limits, response format, permission requirements, or side effects (e.g., debug mode returns raw objects). The schema provides parameter details, but the description adds no behavioral context.

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 succinct (single sentence) but lacks structure. It front-loads the main purpose but omits critical details. It could be more informative without losing conciseness by adding brief usage hints or behavioral notes.

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 has 6 parameters (though only 1 required) and no output schema or annotations, the description is too minimal. It does not explain return values, error conditions, or how the various filters interact (e.g., column vs lines vs summary_only). An agent would struggle to predict behavior beyond the schema.

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 has a clear description in the schema. The tool description adds no semantic value beyond the schema—'context control optional' is vague. With full schema coverage, a baseline of 3 is appropriate; the description does not improve or worsen parameter understanding.

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 'Get sheet content (context control optional)' clearly states the verb and resource. The input schema further clarifies that it retrieves sheet content with optional filters (column, limit, lines, etc.). This distinguishes it from sibling tools like get_column_info or search_sheets, which have different purposes.

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 (e.g., search_sheets, get_snippet). There is no mention of prerequisites, when not to use, or how the 'context control' differs from other retrieval tools. This leaves the agent without decision support.

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