Ensure the Cobalt remote spy is loaded

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

Describes actions as 'load or verify', implying idempotent and non-destructive. No annotations to contradict. However, doesn't detail what 'verify' entails.

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?

Two concise sentences, front-loaded with action. Every sentence adds value without redundancy.

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?

Adequate for a simple, parameterless tool. Specifies usage context. Minor omission: does not clarify idempotency or what happens if spy is already loaded.

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?

Zero parameters; schema coverage 100%. Description adds no param info as none exist. Baseline 4 per instructions.

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?

Explicitly states it loads or verifies the Cobalt remote spy. Distinguishes from siblings by indicating it's a prerequisite for reading, clearing, blocking, or ignoring remote spy logs.

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?

Clearly specifies when to use: before reading, clearing, blocking, or ignoring remote spy logs. Provides actionable context.

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