gmail_get_meeting_notes

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond them: it only returns providers and URLs and deliberately does not fetch external documents, which sets scope expectations.

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?

Three short sentences with no filler; the extraction scope, the return shape, and the read-only nature are each covered once and front-loaded.

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 compensates by stating the return contents (providers and URLs) and the non-fetch behavior. For a one-parameter read tool this is nearly complete; only an explicit mention of the download alternative 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?

Schema coverage is 100% and the single thread_id parameter is fully documented in the schema. The description only echoes the thread-scanning context without adding format or constraint details, so the baseline 3 applies.

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 ('Extracts') and precise resource ('meeting notes links ... from a Gmail thread'), and names the concrete link types (Google Docs from Gemini notes, Read AI reports). This clearly separates it from siblings like gmail_get_thread_summary or gmail_get_attachment.

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 clause 'without downloading external docs' implies that a doc-fetching tool (e.g., drive_get_doc_text) is the alternative when actual content is needed, giving clear contextual guidance. It stops short of explicitly naming that alternative or stating when-not to use this tool.

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