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

With no annotations, the description carries the transparency burden. It discloses that the package is 'receipted', 'machine-queryable', and 'backed by MemoryCrux records', hinting at persistence and side effects. It also describes the included components. It does not explicitly state whether the operation is a write or read-only, but 'provision' strongly implies creating a persistent record.

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 two sentences with no filler. The first sentence defines the tool's purpose and output, while the second efficiently explains scope variations. It is front-loaded with the main action and uses compact, domain-specific notation.

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 provisioning tool with an output schema, the description covers the main content areas and scope semantics. It is missing explicit side-effect or prerequisite information, but the existence of an output schema reduces the need to describe return values. Overall, it is sufficiently complete for an agent to select and invoke the tool.

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?

The schema has 0% description coverage, so the description must compensate. It does explain the 'scope' enum values in detail (minimal, standard, comprehensive), which is valuable. However, it does not elaborate on 'agent_role' or 'operator_id', though these are reasonably self-explanatory from their names and the context of provisioning a new agent.

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 generates a structured, receipted context package for a new agent, with a specific verb and resource. It also distinguishes itself from sibling tools by focusing on provisioning rather than querying context, and includes the equivalent of soul.md, heartbeat.md, and user.md files.

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 description provides clear context for when to use the tool (for a new agent) and explains the three scope levels (minimal, standard, comprehensive), which helps select the right mode. However, it does not explicitly mention when not to use it or name alternative tools, though the 'get_' sibling tools suggest a natural contrast.

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