Meeting Chief Lite

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. While it lists operations, it doesn't describe important behavioral traits like whether this is a read-only operation, authentication requirements, rate limits, pagination behavior beyond the schema's offset/limit, error handling, or what 'stats' returns. For a tool with 5 parameters and multiple operations, this leaves significant gaps in understanding how it behaves.

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 appropriately concise with two sentences that efficiently communicate the tool's purpose and operations. The structure is front-loaded with the core purpose followed by operational details. Every sentence earns its place, though the second sentence could be slightly more structured for clarity.

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 (5 parameters, 4 distinct operations, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns for different operations, how results are structured, error conditions, or behavioral constraints. For a multi-operation tool with no output schema, the description should provide more context about expected outputs and operational boundaries.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning the operations that correspond to the 'operation' enum values, but doesn't provide additional semantic context about parameter interactions or usage patterns. This meets the baseline for high schema coverage.

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 as 'Browse and retrieve meeting transcripts from Otter.ai' with specific operations listed (list, get, recent, stats). It distinguishes itself from the 'search' sibling tool by focusing on browsing/retrieving rather than searching, though the distinction could be more explicit. The verb+resource combination is specific and actionable.

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 implies usage through the listed operations but doesn't explicitly state when to use this tool versus the 'search' sibling tool. It provides operational context (list for all, get for specific, recent for last N days, stats for database info) but lacks clear guidance on tool selection criteria or exclusion scenarios. The implied usage is helpful but not comprehensive.

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