explain_formula_cell

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lower. It adds value by disclosing the analysis scope (direct refs plus upstream and downstream traversal), which is genuine context beyond the annotation. It says nothing about traversal cost on large workbooks, how cycles are handled, or what the explanation output looks like.

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?

A single front-loaded sentence with no filler, and the three analysis outputs are listed in a logical order. It is arguably undersized for a four-parameter traversal tool, but nothing in it is wasteful.

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?

With no output schema, the description must carry return-value information, and it does partially by naming the three result categories. It still leaves max_depth behavior, cycle handling, and output shape unspecified, which is a meaningful gap for a graph-traversal explainer.

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 only 25% – only filepath carries documentation. The description never mentions cell, sheet_name, or max_depth, so it fails to compensate. max_depth is especially consequential (it bounds the upstream chain walk) and is completely unexplained in both schema and 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 names a specific verb (Explain) and resource (formula cell) and enumerates the three things it returns: direct references, upstream formula chain, downstream dependents. That is far more informative than the bare name. It does not, however, contrast itself against close siblings such as inspect_formula, analyze_range_impact, or detect_circular_dependencies, so an agent must infer the boundary.

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?

There is no statement of when to use this tool versus the many adjacent inspection tools in the sibling list. No prerequisites, no exclusions, and no alternative is named. The agent is left to guess between this and inspect_formula or detect_circular_dependencies.

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