get_agent_context

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves current context and session info, including locked files and prior session state. However, it does not address edge cases such as missing context, invalid agent_id, or any potential side effects. The read-only nature is implied by 'Retrieve' but not explicit.

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 well-structured with a main sentence and a bulleted WHEN TO USE section. Each bullet adds a specific scenario, though the RECOMMENDED paragraph partially duplicates the bullets. It's concise and front-loaded.

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 tool with one parameter and no output schema, the description covers the key use cases and recommended timing. It would benefit from noting what happens when no active context exists, but otherwise it's sufficient for an agent to understand when and why to call it.

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 schema already describes the sole parameter 'agent_id' as 'Your agent_id from register_agent() (required)' (100% coverage). The description adds no additional parameter semantics, so baseline 3 is appropriate.

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 identifies the tool's function: 'Retrieve your current work context and session information.' It uses a specific verb and resource. While it doesn't explicitly contrast sibling tools, the WHEN TO USE section implies its scope (active context, locked files, previous sessions), which helps differentiate it from history/log tools.

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 provides an explicit 'WHEN TO USE' list with concrete scenarios (start of conversation, verify objective, see locked files, resume after interruption). It also includes a recommendation to call at the beginning of each conversation. However, it does not mention when not to use or name alternative tools.

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