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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotency, so the safety profile is partly covered. The description adds the embedded-app-only access constraint, but never says which enum actions mutate or destroy data, whether calls are idempotent per action, or what the nested data payload must contain for a mutating request.

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 no filler, and the identifying statement comes first. But the first sentence only echoes the title, so for a tool with 15 actions and a nested payload the brevity crosses into under-specification rather than efficient conciseness.

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 15 enum actions, a required UUID, a free-form nested data object, no output schema, and destructive annotations, the description leaves an agent unable to select an action or build a valid data payload. It anchors the tool's identity and access scope but is far from complete for this complexity.

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% and the description says nothing about the parameters. The action enum has 15 undocumented values whose meanings (grant, pinning, enrichment_state, enrichment_review) are not derivable, and the free-form nested data object is entirely unexplained, so the description fails to compensate for the coverage gap.

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?

"Native sheet editor requests" largely restates the title "Sheet editor transport" and never names a concrete verb or resource. An agent cannot tell what the tool actually does (it is a 15-action multiplexer for snapshot/page/grant/enrichment/view operations) nor how it differs from sheets_get, view_sheet, or the sheets_* siblings it overlaps with.

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?

"Available only to the embedded app" is a genuine access/exclusion constraint that tells an agent when this tool is off-limits. However, there is no guidance on which of the 15 actions to use, and the enum values (grant, enrichment_review, view_reorder) overlap conceptually with dedicated sibling tools, so routing is left entirely to inference.

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