audience_manage_apply

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the safety profile is covered. The description adds genuinely new behavior: a read-back after the write, and that replaying the same key returns the stored result rather than re-executing. It still does not say what the write destroys or what authorization the approval_id carries.

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-loaded with the verb and kept to three short fragments. The trailing 'Writes.' is largely redundant with the first sentence, but overall there is little waste for a terse mutation tool.

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?

An output schema exists, so return values need not be explained. For a destructive, 4-param mutation with 0% schema coverage, though, the description omits what operation does and what args contains, leaving gaps an agent must guess at before invoking.

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% for 4 parameters, so the description must carry the semantics. It names approval_id and idempotency_key and hints at a 'write flag' for operation, but never explains what operation accepts or what the args object carries. The primary payload parameter is left completely ambiguous.

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: executing an accepted Audience write once, with the read-back follow-up. This distinguishes it from audience_manage_prepare (which stages the write), though it does not name that sibling explicitly. The purpose is clear 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 'accepted' and the required approval_id imply this is the apply step after a prepare/approval flow, so usage context is implied. However, it never explicitly says when to use this versus audience_manage_prepare or audience_manage_reconcile, leaving the agent to infer the workflow.

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