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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: an authentication requirement, a hard cap of 100 results, a 'truncated' flag signalling more data exists, and deterministic recency ordering. It also states what the listing deliberately omits, which prevents an agent from assuming a complete inventory.

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?

Front-loads the access requirement and the core action, then layers result shape and exclusions in a single tight block. Every clause carries operational information (auth, cap, truncation, entry fields, exclusions) with no filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields (id, title, kind with its two values, ISO 8601 last-change time) and the truncation signal. For a zero-parameter read tool, nothing needed to call or interpret the result is missing.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It usefully notes that the returned id should be passed as documentId to read_document and the compute tools, which aids chaining even though it is not a parameter of this call.

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 and resource ('List the person's documents that they own') plus ordering ('most recent first') and scope exclusions (folders, archived, trash). This makes it distinguishable from search_documents, whose results would be query-driven rather than an ownership-scoped recency list.

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 a clear precondition ('Needs sign-in') and defines what is out of scope (folders, archived, trash), which tells the agent when this listing is the wrong source. It does not explicitly name search_documents as the alternative for keyword lookups, so routing between the two is left to inference.

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