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

The description reveals that by default only the start of the transcript is included, and that passing transcript=true returns the full transcript instead. It also discloses the output contents (summary, attendees, time, space, link, transcript start), adding value beyond the readOnlyHint annotation.

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 compact and front-loaded, stating what the tool returns in the first sentence. The second sentence clarifies both parameters without unnecessary detail or repetition.

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?

Since there is no output schema, the description adequately enumerates the return contents and explains the default versus transcript mode. This is sufficient for an agent to know what to expect and when to use the transcript flag.

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?

Although the schema already has 100% parameter coverage, the description adds meaningful context: note can be an object id from get_granola_notes, a Granola note id, or a title, and transcript should be used when the user wants exact wording. This goes beyond the schema's brief descriptions.

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 verb and resource: it reads one Granola meeting note and returns the full content. It also distinguishes itself from siblings like get_granola_notes by emphasizing a single note and listing specific fields returned.

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 gives concrete guidance for choosing the transcript versus summary based on the user's request ('when the user asks what exactly was said'). It also explains that the note identifier can come from get_granola_notes, but it does not explicitly contrast this tool with search_granola_transcripts or other alternatives.

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