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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), so the description earns credit for adding boundaries beyond that: it does not start audio, generate coaching, or purchase access, and it does not change the active conversation by default. It also discloses the return value (saved conversation and app URL), which matters since there is no output schema.

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?

Four short sentences, front-loaded with the core action, then return value, then defaults, then exclusions. Every sentence carries information; no filler.

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 9 parameters, 5 required, no output schema and no schema descriptions, the description covers purpose, return shape and default activation but leaves four parameters (speechLanguage, role, company, projectId) with zero explanation. Adequate but incomplete for a parameter-heavy creation tool.

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 0% across 9 parameters, so the description must compensate. It mentions title, notes, existing sources (contextItemIds), the purpose categories, and the activate-by-default behavior, but says nothing about speechLanguage, role, company, or projectId — several parameters remain undocumented anywhere.

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 clear verb+resource: saving a meeting/interview/sales/practice brief in MagicInterview, with the fields it carries (title, notes, sources). It is distinguishable from the sibling read/write/execute tools by being a preparation-creation tool, though it doesn't explicitly name or contrast with them.

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?

Usage is implied ('prepare a meeting or interview') and the default behavior is described ('defaults to meeting preparation without changing the active conversation'), which hints at the activate flag. However, there is no explicit when-to-use guidance versus siblings like magicinterview_app_write or when-not-to-use conditions.

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