enable_subdomain_stripping

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

With no annotations, the description carries the full burden of disclosing behavior, but it only states a mutation ('enable') without detailing side effects, reversibility, prerequisites, or impact on domain handling. This is a significant transparency gap for a configuration-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 extremely short, but this is under-specification rather than effective conciseness. The single sentence merely repeats the tool name and does not use its space to convey useful operational information.

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 two-required-parameter mutation tool with no annotations and 0% parameter coverage, the description is far too incomplete. Even with an output schema present, the agent lacks the domain knowledge needed to call this tool correctly: what sub-domain stripping means, its effect, and any prerequisites.

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 description coverage is 0%, and the description provides no explanation of zoid or domain_name. The agent must guess that zoid identifies an organization/domain context and domain_name is the domain affected; the description adds no meaning beyond the raw parameter titles.

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 'Enable sub-domain stripping.' restates the tool name verbatim, making it tautological. It identifies an action and resource but adds no definition of what 'sub-domain stripping' is or how this tool differs from related domain operations.

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 enable sub-domain stripping, what conditions must be met, or how this tool compares to siblings such as disable_subdomain_stripping or verify_domain. The agent is left to infer usage entirely from the tool name.

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