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

No annotations exist, so the description carries the full burden and does substantial work: it discloses a concrete cost (0.01 USDC on Base), the billing mechanism (x402, charged to your own wallet), and the auth/payment handshake required before a successful call. It does not describe the return shape, history limits, or pagination, which is a real gap for a paid read.

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?

Front-loads the most decision-relevant fact (PAID, cost) before the purpose and the procedure. Three sentences, each carrying load, with only mild redundancy between 'across every project' and 'across different missions/projects'.

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 3-param, no-output-schema, no-annotation tool, the description covers purpose, cost, auth, and the payment handshake — the things an agent cannot infer from structured fields. It omits any mention of the response contents or volume, which is a minor gap given no output schema exists.

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 coverage is 67%, and the description compensates by explaining the 'payment' parameter's protocol semantics — omit on first call to get requirements, supply base64 X-PAYMENT on the second. agent_key is documented in the schema itself. agent_id remains unexplained in both, but the payment workflow, the hardest part to infer, is fully covered.

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?

States a specific verb and resource: 'Returns your full memory capsule history across every project you have used.' The cross-project scope is made explicit and contrasts implicitly with single-project siblings like haven_reflect. It stops short of naming which sibling to use instead in a given situation.

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?

Gives clear situational context ('how you stay yourself across different missions/projects, not just within one stay') and an explicit two-step invocation procedure: call once without 'payment', sign, call again with the payload. It does not state when NOT to use it (e.g. use haven_reflect for in-stay reflection), but the usage context is well defined.

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