Convo

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

No annotations are provided, so the description carries full burden. It describes output content but doesn't disclose behavioral traits such as authentication needs, rate limits, data sources, or potential side effects (e.g., if it triggers notifications or modifies data). For a read operation with zero annotation coverage, this is a significant gap in transparency.

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 front-loaded with the core purpose in the first sentence, followed by specific content details in a concise list. Every sentence earns its place by clarifying scope and output, with no redundant or vague language, making it highly efficient 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 moderate complexity (consolidated analytics), no annotations, and no output schema, the description is partially complete. It covers purpose and output content adequately but lacks details on behavioral aspects and return format, leaving gaps that could hinder an agent's effective use without further context.

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%, with the parameter 'days' fully documented in the schema (number, range 1-90, default 7). The description adds no additional parameter semantics beyond implying a time period, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for gaps.

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 a consolidated digest of all your meetings over a time period' with specific content details (total meeting time, decisions, action items, per-meeting summaries). It distinguishes from siblings like 'get_summary' (singular) or 'list_meetings' (raw listing) by emphasizing consolidation and comprehensive analytics. However, it doesn't explicitly name alternatives, keeping it at 4 rather than 5.

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 context ('over a time period') and content scope, suggesting it's for retrospective analysis rather than real-time or future-focused tasks. However, it lacks explicit guidance on when to use this versus alternatives like 'find_action_items' (specific extraction) or 'get_summary' (single meeting), and doesn't mention prerequisites or exclusions, leaving usage somewhat inferred.

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