sheets_get_conditional_formatting

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

Discloses normalization behavior (English locale, semicolons to commas), the option to disable it, and the inclusion of the _formulaLocaleRaw field. Since no annotations are provided, the description fully covers 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?

Three sentences, no redundant information. Key points are front-loaded (purpose first), and every sentence contributes unique value.

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?

Adequately covers the tool's functionality for a read operation with three parameters. Could mention that no output schema is provided, but the description implies the return type. Lacks mention of any limits or error conditions.

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 coverage is 100%, but the description adds value by explaining the normalizeFormulas parameter's default behavior and its effect on formula output, going beyond the schema's simple type/description.

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 specifies reading conditional formatting rules and banded ranges, a specific verb-resource pair. It clearly distinguishes from sibling tools like sheets_add_conditional_formatting (write) and sheets_get_sheet_formatting (different focus).

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?

No guidance on when to use this tool versus alternatives (e.g., sheets_get_sheet_formatting) or when not to use it. The description is purely declarative.

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