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

Annotations declare the mutation/safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds real context beyond them: draw.io/Mermaid/SVG bypass AI, import_only returns text with no flow, and only files Wavelength created or the user picked can be opened. The disconnected-Drive error behavior is also disclosed. No contradiction with the annotations.

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 core purpose is front-loaded in the first clause, and each subsequent sentence carries distinct information (file types, import_only mode, access restriction, error handling). The file-type list is a bit dense but earns its place by defining supported inputs.

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 covers supported inputs, the import_only return mode, access constraints, and error behavior for an 8-parameter (all optional) tool. It could say more about the returned flow/text shape, but for this tool the coverage is solid.

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 100%, so the schema already documents all eight parameters; baseline is 3. The description reinforces import_only semantics ('get the text back without making a flow') but adds no syntax, format, or default details beyond what the schema fields already state.

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 (read) and resource (Google Drive file) and the resulting action (make a flow), then anchors it to a named sibling with 'the same way as create_flow_from_text'. It also enumerates the file types it consumes, so an agent can distinguish it from text- and diagram-based siblings without opening the schema.

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?

Gives clear context: use it to import from the connected Drive, with 'import_only' as an alternative mode that returns text instead of creating a flow, and notes the Drive-connection prerequisite and its error behavior. It lacks explicit when-not guidance versus other import siblings (e.g. import_diagram, import_from_n8n), so it falls short of a full 5.

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