FastMCP Google Docs Manager

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool reads text content, implying a read-only operation, but doesn't cover aspects like authentication needs, rate limits, error handling (e.g., for invalid IDs), or what happens if the document is inaccessible. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Read the text content'), making it easy to scan and understand quickly. Every part of the sentence contributes essential information.

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 the tool's low complexity (one parameter) and the presence of an output schema (which handles return values), the description is somewhat complete but lacks depth. It covers the basic action but misses behavioral context (e.g., permissions, errors) and usage guidelines. With no annotations and minimal parameter explanation, it's adequate but has clear gaps for effective agent use.

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?

The description adds minimal meaning beyond the input schema: it clarifies that 'doc_id' refers to a Google Doc's document ID. However, with 0% schema description coverage (the schema has no descriptions for parameters), the description doesn't fully compensate by explaining format, examples, or constraints (e.g., ID structure). Since there's only one parameter, the baseline is higher, but more detail would improve clarity.

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 clearly states the action ('Read the text content') and resource ('a Google Doc by its document ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'list_documents' (which lists documents) or 'create_document' (which creates new ones), but the verb 'Read' versus 'list' or 'create' provides implicit distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid document ID), exclusions (e.g., not for binary files), or comparisons to siblings like 'list_documents' for browsing documents first. Usage is implied by the action but not explicitly stated.

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