Hardened Google Workspace MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this is a deletion operation (implying mutation/destructive action), it doesn't disclose important behavioral traits like permission requirements, whether the deletion is permanent/reversible, error handling for invalid indices, or rate limits. The description adds minimal behavioral context beyond the basic operation.

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 perfectly structured and front-loaded: the first sentence states the core purpose, followed by well-organized Args and Returns sections. Every sentence earns its place by providing essential information without redundancy. The formatting with clear section headers enhances 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 the tool's complexity (destructive operation with 4 parameters), no annotations, and 0% schema coverage, the description does well by documenting all parameters and return values. However, it could provide more context about authentication requirements, error conditions, or the format of the returned 'current rule state'. The presence of an output schema helps but doesn't fully compensate for missing behavioral details.

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 0% schema description coverage, the description fully compensates by providing detailed parameter documentation in the Args section. Each parameter is clearly explained with its purpose, data type, required status, and default behavior (e.g., 'Defaults to the first sheet if not provided' for sheet_name). This adds substantial meaning beyond the bare schema.

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 specific action ('Deletes'), target resource ('an existing conditional formatting rule by index on a sheet'), and distinguishes from sibling tools like 'add_conditional_formatting' and 'update_conditional_formatting'. It precisely defines what the tool does without being tautological.

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 clear context for when to use this tool (to delete conditional formatting rules by index) and implicitly distinguishes it from sibling tools like 'add_conditional_formatting' and 'update_conditional_formatting'. However, it doesn't explicitly state when NOT to use it or mention alternative approaches for rule deletion.

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