Metis — Toggle Context

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions that 'name must exist in specialist_contexts' but does not disclose side effects (e.g., whether toggling is idempotent, what happens if already active, or any impact on ongoing 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 concise: one line for purpose and a bulleted list for arguments. It is appropriately front-loaded with the action. No superfluous words, though the args section could be integrated more naturally.

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?

Despite having an output schema (not shown), the description fails to mention return values, error conditions, or the overall effect of toggling. For a simple toggle tool, the description is incomplete; it does not convey what happens after activation/deactivation (e.g., context becomes available/unavailable).

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?

Since input schema descriptions are missing (0% coverage), the description adds meaning: it clarifies 'name' as 'Context name to toggle (must exist in specialist_contexts)' and 'active' as 'True to activate, False to deactivate.' This provides necessary constraints and meaning beyond the schema.

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 states the tool's action: 'Activate or deactivate a specialist context.' The verb 'toggle' is clear, and the resource 'specialist context' is specific. It distinguishes from sibling tools like 'add_specialist_context' (which creates new contexts) and 'get_context' (which reads state).

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?

No guidance is provided on when to use this tool versus alternatives like 'add_specialist_context' or 'get_context'. There is no discussion of prerequisites, such as the need for the context to exist, nor any mention of when not to use this tool.

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