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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description adds genuinely new behavior: no platform token exists, the call writes a record, it returns publish_state NOT_PUBLISHED, and it is refused without confirm. It does not address the non-idempotent hint (e.g. whether repeated calls create duplicate intents), which is the one remaining behavioral gap.

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?

Three short sentences, zero filler, with the most important constraint (publishes nothing) front-loaded right after the purpose. Every sentence carries distinct information.

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 no output schema, the description usefully names the returned publish_state value, which is good. However, for a four-parameter write tool with low schema coverage it omits the timestamp format for 'when', acceptable values for 'platforms', and duplicate-call behavior, leaving real gaps an agent would hit at invocation time.

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 25% across four parameters, so the description must compensate and largely does not. It restates the confirm requirement already documented in the schema, but leaves 'when' (no format given), 'platforms' (no valid values), and 'job_id' entirely unexplained.

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 ('Record a publish intent for the Empire Distributor') and immediately corrects the misleading name by clarifying that nothing is actually published. An agent can distinguish this from a real posting tool like clipwright_tiktok_post_draft without opening any 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 confirm=true prerequisite and the 'publishes nothing' caveat give implied usage context, but there is no explicit statement of when to choose this over alternatives such as clipwright_tiktok_post_draft, nor any when-not guidance. The agent must infer that this is the intent-recording path rather than the actual publishing path.

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