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

With no annotations, the description carries the full burden of behavioral disclosure, yet it says nothing about return format, whether it requires an ID, permission requirements, or error behavior. It only weakly implies a read operation via 'get'.

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?

It is a single short sentence with no padding, but the generic 'Run Google docs action:' prefix is low-value filler rather than a meaningful front-loaded statement of the operation.

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?

For a retrieval tool with no output schema and no annotations, the definition should explain what is returned and whether an identifier is needed. None of that is present, leaving significant gaps an agent cannot resolve from the other fields.

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 100%, so the single 'detail' parameter is documented in the schema itself, giving the baseline of 3. The description adds no interpretation of what 'detail' should contain, but the schema-coverage rule caps the concern here.

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 phrase 'get doc' names a verb and resource, so the basic operation is inferable, but it is wrapped in generic boilerplate ('Run Google docs action:') that adds nothing and the definition reads as a near-restatement of the tool name. It gives no signal to distinguish it from siblings like docs__list_docs or docs__converse.

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 indication of when to use this tool rather than docs__list_docs for enumeration or docs__converse for content work. No prerequisites, exclusions, or alternative selection logic are provided.

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