activate_domain

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the primary effect—'make its tools available'—but does not explain side effects, idempotency, whether activating one domain deactivates another, persistence, or error behavior. This is a thin disclosure for a state-changing tool.

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 and front-loaded with action and purpose, followed by a list of valid domains and a pointer to list_domains. The domain list repeats the schema enum, but it serves as a convenient inline reference without being overly verbose.

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?

The tool is simple with a single parameter and no output schema, so the description covers the basics: what to activate, the valid domains, and how to check status. However, it leaves the activation model under-specified—particularly whether domains are mutually exclusive or cumulative—and does not mention deactivate_domain as the reverse operation.

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% and the schema already describes the domain parameter with an enum and 'Domain name to activate.' The description adds no meaningful semantics beyond listing the same enum values, so it does not exceed the baseline.

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 states a specific verb and resource: 'Activate a domain to make its tools available.' It lists all valid domain values, making the tool's scope explicit, and its purpose is clearly distinct from siblings like deactivate_domain and list_domains.

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 explicit guidance to 'Call list_domains to see current activation status,' directing the agent to the appropriate sibling for checking state. It does not explicitly contrast with deactivate_domain or describe when activation is unnecessary, but the core usage context is clear.

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