get_recent_google_docs

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

The annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds value by specifying the scope ('most recently modified'), which is not covered by annotations. However, it does not disclose additional behavioral traits such as rate limits, authentication needs, or pagination behavior. No contradiction with annotations exists.

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: 'Get the most recently modified Google Documents.' It is front-loaded with the core purpose and contains no unnecessary words or redundancy, making it highly concise and well-structured.

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 (2 parameters, no nested objects), the presence of annotations (readOnlyHint), and an output schema (which handles return values), the description is reasonably complete. It specifies the scope of retrieval but could benefit from more context on usage versus siblings. Overall, it provides adequate context for a simple read operation.

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 input schema has 100% description coverage, with clear documentation for both parameters (max_results and days_back). The description does not add any parameter-specific semantics beyond what the schema provides, such as default values or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema carries the burden.

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 tool's purpose: 'Get the most recently modified Google Documents.' It specifies the verb 'Get' and resource 'Google Documents' with the qualifier 'most recently modified.' However, it does not explicitly differentiate from sibling tools like 'list_google_docs' or 'search_google_docs,' which may offer similar functionality, so it lacks full sibling 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 does not mention sibling tools like 'list_google_docs' or 'search_google_docs,' nor does it specify contexts where this tool is preferred or excluded. Usage is implied by the name 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.