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

No annotations are provided, so the description must carry the full behavioral burden. 'Guarded exactly-once' is a useful trait, but there is no disclosure of side effects, permissions, error handling, or what happens on repeat calls, which is especially important for an execution tool.

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 sentence and front-loads the core behavior. However, it is a fragment that omits necessary context, making it concise at the expense of helpfulness.

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?

For a tool with 6 parameters, no annotations, no output schema, and nested payload objects, the description is far too thin. It gives only a high-level phrase and an endpoint, leaving an agent unable to call it correctly without external knowledge.

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?

All 6 parameters have 0% schema description coverage, and the description does not mention any of them. Required fields like run_id, checkpoint_ns, node, effect_key, and kind, plus optional payload, are left completely 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?

The description names a specific verb ('execution') and resource ('effect') and adds the endpoint POST /effects/execute. It is distinguishable from siblings like resume_record_effect, but it does not explicitly contrast itself with them.

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?

There is no guidance on when to use this tool versus the sibling tools (e.g., resume_record_effect or resume_audit_journal). The only hint is 'guarded exactly-once execution', which implies idempotent semantics but does not tell the agent when to choose this tool.

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