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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: no note on why a create is flagged destructive, whether retries duplicate agents, or what side effects the webhook/audio stream registration has.

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?

A single tight sentence with the key concept ('shortcut for creating an external_audio agent') front-loaded and no filler. It is efficient, though its brevity contributes to the specification gaps noted elsewhere.

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?

A destructive create operation with 5 parameters, 20% schema coverage, and no output schema needs more than one sentence. The description omits parameter significance, side effects, and any return/identity information, leaving an agent under-informed before a non-idempotent write.

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 only 20% (just organization_id), so the description must compensate, and it covers only webhook_url and audio_stream_url by name. It says nothing about name, project_id, or the expected URL format, leaving three required-ish fields undocumented.

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 outcome: it creates an external_audio agent preconfigured with webhook and audio stream URLs, and labels itself a shortcut, which implicitly differentiates it from the sibling create_agent. An agent can grasp the resource and scope without opening the schema.

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 word 'shortcut' implies this is the preferred path when the target is an external_audio agent, so usage is implied. However, it never names create_agent as the alternative, states no prerequisites, and gives no when-not guidance.

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