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

The description goes well beyond annotations by detailing side effects (stores a new prompt and result, leaves original untouched), the reproducibility field and its conditions, and the lineage semantics. It does not contradict any annotation and adds substantial behavioral context, which is critical for a tool with destructiveHint=true and no output schema.

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 dense paragraph with many technical details (lineage, reproducibility, sim_edges/sim_neighbors). It is not poorly written but lacks structure; it could benefit from bullet points or clear separation of concepts. It is comprehensive but slightly verbose for a 3-parameter 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?

The description covers the core behavior, side effects, override rules, and the reproducibility check, which is the key output detail. Given there is no output schema, it explains the main return nuance but does not fully specify the entire response shape. It also references how to query results via sim_edges/sim_neighbors, which adds context. Overall very complete for a tool with this complexity.

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 each parameter (text, prompt, system) is already documented with override behavior. The description restates the default reuse ('Reuses the original prompt's text and system unless you override them here') but adds no new meaning beyond what the schema provides. The prompt parameter's role as an id is also clear in the schema. Baseline 3 applies.

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 re-runs a stored sim_prompt against the same parent, and explicitly distinguishes it from a chain by explaining it never derives from previous output. It names the resource (stored prompt) and the action (re-run), and the sibling contrast is implicit but strong.

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?

It explains when to use it: to re-run a stored prompt against the same parent, and clarifies the lineage behavior (siblings not chain). It also notes overrides and when reproducibility is checked. However, it does not explicitly mention alternatives like sim_prompt for new prompts, but the context implies the distinction.

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