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

Annotations already declare destructive=true, readOnly=false, idempotent=false, openWorld=true, so the safety profile is covered; the description adds genuinely new context — the edit-permission requirement and the reassurance that cell values are untouched, which bounds the blast radius. It does not say what happens when the id is missing or unknown, keeping it below 5.

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?

Two short sentences with the destructive action front-loaded, followed by permission and scope caveats — no filler. The trailing signature line partly duplicates the schema and is the only mildly wasteful element.

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?

An output schema exists and annotations cover the destructive/idempotency profile, so the description only needs to supply permission expectations and scope, which it does. It leaves error behavior for an invalid or already-deleted id unspecified, a minor remaining gap.

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 67%; id and sheet are documented in the schema, and the description reinforces id's provenance and sheet's optionality via the signature line. file_uuid has no description in either place, so the description does not compensate for that gap. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Removes a conditional formatting rule by its id') and names the sibling that produces the id (files_conditional_formats), which also disambiguates it from files_set_conditional_format and the other files_delete_* tools.

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?

Tells the agent where the id must come from and that edit permission is required, which is the key precondition for calling it. It does not explicitly say when not to use it (e.g. to modify rather than remove a rule, use files_set_conditional_format), so it stops short of full alternative routing.

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