wake-session

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

With no annotations provided, the description carries full burden. It discloses that the tool enables secret access and mentions optional restrictions (scope) and auto-sleep behavior. However, it doesn't cover important behavioral aspects like authentication requirements, error conditions, what happens if called multiple times, or whether this affects other users/sessions.

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 appropriately concise with two sentences that efficiently convey the core purpose and key optional features. The first sentence states the primary action, and the second covers the two parameters. No wasted words, though it could be slightly more front-loaded by mentioning parameters in the first sentence.

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 session management tool with 2 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It covers the basic purpose and mentions parameters but lacks details about side effects, prerequisites, or what 'waking' actually entails operationally. Given no annotations, more behavioral context would be helpful.

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 description coverage is 100%, so the schema already fully documents both parameters. The description adds minimal value by mentioning the parameters exist ('restrict access to specific tag scope and set auto-sleep timer') but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 action ('wake/unlock') and resource ('session') with the purpose 'to start accessing secrets'. It distinguishes from sibling 'sleep-session' by being the opposite operation. However, it doesn't explicitly differentiate from other session-related tools like 'session-status' or 'onboard'.

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 description implies this should be used before accessing secrets ('to start accessing secrets'), suggesting a prerequisite relationship with secret-access tools. However, it doesn't explicitly state when NOT to use it (e.g., if session is already awake) or mention alternatives like 'session-status' to check current state first.

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