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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that the record is sealed with a commitment to the authenticated principal, that Knox does not authenticate the named agent, that the event carries `agentIdentityVerified:false`, and that the record makes an independently checkable assertion. This is rich, transparent behavioral context that goes far beyond a simple action statement.

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 long sentences, but every clause adds substantive value—purpose, event type, metadata fields, and the critical trust model. It is dense but not wasteful; the front-loaded purpose is immediately clear. It could be slightly tightened, but for the conceptual complexity it is well-structured.

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?

Given the absence of annotations and output schema, the description is remarkably complete. It covers the event's content, the trust boundaries, the principals involved, and the verifiable nature of the record. Combined with fully described schema parameters, an agent has everything needed to use the tool appropriately.

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 input schema has 100% description coverage, so the baseline is 3. The description does not add per-parameter meaning beyond what the schema already provides; it gives high-level context about digests and agent identity, but the schema descriptions already explain the assertion semantics and formats. The description neither compensates for gaps nor loses credit.

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 records an `agent_mcp_tool_call` event with structured metadata, naming the specific event type and its purpose as a 'convenience anchor' for AAM MCP. It distinguishes itself from generic anchoring by focusing on tool-call auditing, but it does not explicitly contrast with the sibling `anchor_event` tool, so it falls short of full differentiation.

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 implies when to use the tool—when you need to anchor an MCP tool call and record its metadata—but it does not explicitly state when not to use it or how it compares to alternatives like `anchor_event` or `anchor_file_hash`. The usage context is clear enough to infer, but there is no explicit routing guidance.

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