export_snapshot

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

With no annotations provided, the description carries full responsibility for disclosing side effects, output characteristics, or whether the operation is read-only. 'Full State Snapshot' reveals nothing about behavior beyond the tool's name, leaving the agent completely in the dark.

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 extremely brief, but this is under-specification rather than effective conciseness. A three-word noun phrase does not provide enough content to fulfill the tool's documentation purpose, mirroring the 'Process' example.

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 lack of annotations, output schema, and parameters, the description needed to explain what 'full state' includes, how the snapshot is returned, and how to interpret results. It provides none of this, making the tool nearly unusable for an AI agent 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?

The tool has zero parameters, so the schema contains no properties to document. Per baseline rules, a 0-parameter tool receives a 4 for this dimension, even though the description adds no parameter-related value.

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 'Full State Snapshot' is essentially a restatement of the tool name 'export_snapshot'. It does not include a specific verb or clarify what the snapshot contains, and it fails to distinguish from sibling tools like get_system_status or orch_report.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about typical use cases, prerequisites, or situations where another tool would be more appropriate.

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