snapshot

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

Discloses read-only nature, no generative model calls, no writes. Mentions always fetching memory/run/calibration and conditional activation. Without annotations, this is fairly transparent.

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?

Concise, front-loaded with main purpose, then details. Could be slightly more structured but not overly long.

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?

Despite lacking annotations and output schema, the description fails to explain parameter usage and only partially describes return format. An agent cannot confidently set parameters without additional context.

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?

With 13 parameters and 0% schema coverage, the description only hints at 'goal' and 'problem' for activation fetch. No guidance on the other 11 parameters (files, top_k, region, etc.), leaving the agent uninformed.

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?

Clearly states the tool creates a brain state snapshot, returns structured data, and is read-only. Distinguishes from siblings by mentioning CLI rendering and the conditional activation fetch.

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?

Explains when to use (visualization, obtaining serializable data) and when activation is fetched (only when problem/goal non-empty). Lacks explicit comparison with alternatives but still clear.

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