add_meeting

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

With no annotations, the description carries the full burden. It explains the action and the local storage behavior, but lacks details on constraints (e.g., duplicate titles, size limits), idempotency, or side effects. The description is adequate but not thorough for a mutation tool.

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 concise and well-structured: a brief purpose/usage sentence, then a clear arg list. Every sentence adds value, and the information is front-loaded. No wasted words.

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 has an output schema (not shown), the description needn't cover return values. It covers purpose, usage, and parameter details adequately. It could mention error conditions or constraints, but for a simple creation tool with rich parameter descriptions, it is sufficiently complete.

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?

Despite 0% schema description coverage, the description provides explicit, helpful explanations for all three parameters: title is a short title with an example, transcript is full raw text, meeting_date is ISO format and optional with an example. This fully compensates for the lack of schema 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 'Store' and resource 'meeting transcript', and specifies the action is local storage for future search/reference. It distinguishes from sibling tools like get_meeting, list_meetings, and search_meetings, which are retrieval-focused.

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 explicitly says 'Call this whenever the user shares a new meeting transcript', providing clear usage context. However, it does not mention when not to use it or alternatives, which would be helpful but is not critical given the sibling tool names imply different purposes.

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