tool_enable

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

No annotations are provided, so the description bears full responsibility. It discloses activation and listing behavior but omits important details like session scope, side effects, permissions required, or what 'activate' entails (e.g., success response, error states). Minimal behavioral disclosure.

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 sentences, front-loaded with the primary action, no wasted words. Every sentence provides value: action and usage variant.

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 no output schema and a single parameter, the description should clarify what happens upon activation (e.g., confirmation, tool enabled for the session). It only implies listing behavior but does not describe activation outcome or return value, leaving the agent underinformed.

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 coverage is 100% with the description 'Tool name (omit to list available tools)'. The tool description adds 'Use without arguments to list available tools', which reinforces but does not add significant new meaning beyond the schema. Baseline 3 appropriate due to high coverage.

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 tool activates an advanced tool for the session, using 'Activate' as the verb and specifying 'advanced tool'. It differentiates from the sibling 'tool_disable' by implication, though not explicitly.

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?

Provides clear usage guidance: 'Use without arguments to list available tools'. However, lacks guidance on when to use this tool versus the sibling 'tool_disable' or other alternatives, and no explicit 'when not to use'.

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