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

No annotations are provided, so the description carries full responsibility. It discloses concrete side effects: status flips from 'approved' to 'executed', metadata fields set, proof_asset persistence to P9 brain, and queueing of chiefmo_post_launch_review. It also warns about the outcome of non-use. This is exceptionally transparent for a tool with no structured safety hints.

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?

The description is a single, well-structured paragraph that front-loads the trigger with 'USE WHEN'. Every sentence contributes: condition, action, effects, consequence. It avoids redundancy with the schema and is free of fluff.

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?

The description covers trigger, workflow, side effects, and downstream actions. However, it does not describe the return value or any failure modes, which would be useful given there is no output schema. Still, it provides enough context for an agent to decide correctly and invoke the tool with confidence.

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 100%, so the baseline is 3. The description adds workflow context but does not add per-parameter meaning beyond what the schema already provides. For example, actionId is described in schema as being from chieflab_use_manual_fallback, and notes persistence is already implied by schema. No significant extra parameter-level insight is offered.

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?

The description clearly states the tool's function with specific verbs: 'Records the URL on the original publishAction', 'persists a proof_asset', and 'queues 24-hour metrics readback'. It distinguishes from sibling tools by explicitly referencing chieflab_use_manual_fallback and warning that without it, manually-posted channels are lost to the measurement loop.

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?

Opens with 'USE WHEN' and precisely defines the trigger: after the user has manually posted to a channel returned by chieflab_use_manual_fallback. It also explains the consequence of not using the tool, providing implicit when-not-to-use. The workflow context (feeding URL back) is clear and differentiates from alternatives.

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