provenance__recall

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

No annotations provided, so description must self-disclose. It reports quarantining all transitive descendants and flagging the agent. However, lacks details on reversibility, required permissions, or whether the source agent is also quarantined (only 'flagged').

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?

Two concise sentences with zero waste: first covers action, second covers output. Information is front-loaded and efficient.

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?

Reports output (which agents quarantined) but no output schema. Lacks error handling, format of the report, or prerequisite conditions. Adequate but not fully complete for a recall operation.

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 has 0% description coverage. Description explains agent_id implicitly but does not describe the 'reason' parameter at all, leaving the agent without guidance on its purpose or constraints.

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?

Description clearly states the action ('Recall an agent') and its effects ('flags it and quarantines every transitive descendant'), distinguishing it from sibling tools like provenance__lineage which likely only show lineage without recall.

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?

Implied usage: use when needing to recall an agent and quarantine descendants. No explicit when-to-use or when-not-to-use guidance, nor alternatives mentioned despite many sibling tools that could serve similar but different purposes.

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