gworkspace-mcp

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

With no annotations, the description carries full burden but provides minimal behavioral context. It mentions rule types and an example for CUSTOM_FORMULA, but lacks details on permissions, side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this is inadequate disclosure of behavioral traits.

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 brief and front-loaded with the core purpose, followed by rule details. Both sentences add value: the first states the action, the second clarifies parameter usage. No wasted words, though it could be more structured for readability.

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 6 parameters with 0% schema coverage, an output schema exists, and no annotations, the description is incomplete. It covers some parameter semantics but misses behavioral context and usage guidelines. The output schema helps, but the description doesn't fully compensate for the lack of annotations and low schema coverage.

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 0%, so the description must compensate but only partially does. It explains rule_type values and condition_value for CUSTOM_FORMULA, covering 2 of 6 parameters. Other parameters like spreadsheet, sheet_name, range_a1, and bg_color remain undocumented, leaving significant gaps in 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 clearly states the action ('Add conditional formatting') and resource (spreadsheets), making the purpose evident. It distinguishes from siblings like sheets_format or sheets_add_validation by specifying conditional formatting, though it doesn't explicitly contrast with them. The verb+resource combination is specific but lacks explicit sibling differentiation.

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 is provided on when to use this tool versus alternatives like sheets_format for general formatting or sheets_add_validation for data validation. The description lists rule types but doesn't explain context or prerequisites, leaving usage unclear relative to sibling tools.

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