context_manage

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It lists actions but does not explain side effects, whether operations are destructive, or what 'status' and 'release_objects' entail. The description lacks critical details about state changes and requirements.

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 and grammatically structured as a single list, but it is under-specified. It lacks the detail needed to be effective, so the brevity is a deficiency rather than a virtue.

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 tool's complexity (6 parameters, multiple actions, an output schema, and nested spec objects), the description is grossly insufficient. It fails to explain the tool's role within the wider context of sibling tools or how the parameters relate to the actions.

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 has zero parameter descriptions, and the description does not compensate by explaining the parameters. The action enum is mentioned, but parameters like context_id, backend, wave_specs, and design_spec are completely unexplained, leaving the agent without meaning for these fields.

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 explicitly lists the operations (open, reload, close, list, get status, release) and identifies the resource (context objects), making the tool's purpose clear. It does not explicitly differentiate from sibling tools, but the scope is distinct enough to be understood.

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 no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context. It implies usage only through the listed actions, leaving the agent without sufficient decision support.

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