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 creates a new document, implying a write operation, but does not disclose any behavioral traits such as permissions required, whether the creation is idempotent, rate limits, or what happens on failure. This is a significant gap for a mutation tool with zero annotation coverage.

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, clear sentence that efficiently conveys the core purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance. Every part of the sentence earns its place by specifying the action, resource, and parameters.

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 complexity (a mutation with 2 parameters), no annotations, and an output schema present, the description is partially complete. It covers the basic purpose and parameters but lacks behavioral context like permissions or error handling. The existence of an output schema means return values are documented elsewhere, but the description should still address key usage aspects for a creation tool.

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 meaning by specifying that the parameters are for 'title and body content', which maps directly to the two parameters in the schema (title and content). However, with 0% schema description coverage, the schema provides no details about these parameters. The description compensates somewhat by naming them, but does not provide format, constraints, or examples, leaving gaps in understanding.

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 ('Create a new Google Doc') and specifies the resource ('Google Doc'), which is a specific document type. It distinguishes from siblings like 'list_documents' and 'read_document' by focusing on creation rather than listing or reading. However, it doesn't explicitly differentiate from potential other creation tools beyond the context provided.

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 like 'list_documents' or 'read_document'. It lacks any mention of prerequisites, such as authentication needs or when creation is appropriate versus reading existing documents. There is no explicit when/when-not usage context.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists files but doesn't describe any behavioral traits such as authentication requirements, rate limits, pagination behavior, or what happens if no documents exist. This leaves significant gaps in understanding how the tool behaves in practice.

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, clear sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 optional parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete parameter coverage, it lacks details on behavioral aspects and usage context, making it only partially complete 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 mentions no parameters, while the input schema has one parameter ('max_results') with 0% schema description coverage. Since the description doesn't add any parameter information beyond what the schema provides (which is minimal), it meets the baseline of 3 for having no parameter details in the description when schema coverage is low.

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 ('List') and resource ('Google Docs files from your Google Drive'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_document' or 'read_document' beyond the obvious action difference, which prevents a perfect score.

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 like 'read_document' or 'create_document'. It doesn't mention any prerequisites, context for usage, or exclusions, leaving the agent to infer usage based on tool names alone.

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

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.