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

The description helpfully discloses that this writes a synthetic marker row, moves no funds, is never fee-gated, and is a no-op on repeat calls with the same caller_id. However, this idempotency claim directly contradicts the annotation idempotentHint=false. Because the description contradicts a structured hint, behavioral transparency fails.

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 compact and front-loaded with the primary action. The pipeline reference is somewhat arcane, but it earns its place by connecting the tool to its consumer. Overall it is efficient with no filler.

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?

With one optional parameter, an output schema, and clear statements about when to call, safety, and repeat behavior, the description is nearly complete. The main defect is the idempotency contradiction; otherwise an agent has enough context to invoke it correctly.

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 provides only a type and default for caller_id with 0% description coverage. The description adds meaning by saying the caller_id should be your own stable identifier and that repeating the same caller_id is a no-op. It does not specify format or uniqueness constraints, but it compensates reasonably for a single optional parameter.

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 identifies the action ('Self-report'), the resource ('an MCP-registry install/discovery event'), and the specific pipeline context ('registry_install inbound-artifact leg'). It distinguishes this from generic registry or agent registration tools among the large sibling list.

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 gives explicit when-to-use guidance: call once after the server installs/discovers Crank via an MCP registry listing, and use a stable caller_id. It does not explicitly name alternatives or exclusions, but the context is specific enough for an agent to know when this tool applies.

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