Paperclip runtime context

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

The description goes beyond the readOnly and idempotent annotations by explaining the conditional return behavior: Markdown inline when within token threshold, otherwise an immutable snapshot path. This is valuable behavioral detail that the annotations do not convey.

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: the first sentence states the core read action, and the second sentence adds the return behavior. Every sentence earns its place 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?

For a zero-parameter tool, the description sufficiently explains the two return modes and the no-API-call nature. A small gap is that it does not enumerate what the 'run/wake environment' actually contains, though the Markdown return is described as LLM-friendly.

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 there is no parameter semantics burden on the description. The schema is fully covered vacuously, and the description does not need to explain parameter meaning.

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 'Read the current Paperclip run/wake environment', which is a specific verb and resource. It also distinguishes the tool by noting it works 'without an API call', but it does not explicitly differentiate it from the similar sibling paperclip_heartbeat_context.

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 phrase 'without an API call' implies this should be used when a lightweight, low-cost read of the current runtime environment is needed. However, the description does not explicitly state when to prefer this over siblings like paperclip_heartbeat_context or paperclip_raw, nor does it provide exclusions.

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