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

Goes well beyond the annotations: auth requirement, that nothing in a message changes project state, triage timing, dedup semantics on message_id, body/subject size caps, and a specific withholding rule for mail reports over 1500 characters or containing quoted email. The reply-as-draft-task flow is exactly the kind of side effect an agent needs disclosed before calling.

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?

Front-loads the connector restriction and the core action, then layers constraints. Dense but mostly earning its place; the 3500-character limit and idempotency restate the schema/annotations, which is minor redundancy.

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?

With an output schema present and annotations covering safety and idempotency, the description supplies the remaining critical context: auth, triage cadence, no state mutation, content restrictions for mail reports, and the reply path. Only the sibling-routing question is left unaddressed.

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 coverage is 80%, so the schema already documents message_id dedup, the subject/body length limits and task_id. The description reinforces message_id practice ('fresh id per message, retries collapsed') but repeats the 3500-character body cap verbatim and says nothing about task_id or how kind affects handling. Baseline 3.

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 specific verb and resource ('Send a question, finding, proposal or blocked report to the studio's supervisor inbox') and enumerates the kinds it accepts, so the action is unambiguous. It does not, however, contrast itself with plausible siblings like brief_for_joe or submit_task_result, leaving the agent to infer the boundary.

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?

Gives clear operating context: restricted to the referencesource Muse connector with a bearer token, messages are triaged each morning, and replies arrive as draft tasks for Joe's approval with an explicit 'never reply unprompted' exclusion. Missing is an explicit statement of when to prefer this over brief_for_joe or submit_task_result.

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