Make Hosting Dir

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: recursive parent creation and the interaction with deploy_site's auto-create behavior. It stops short of error/naming-collision behavior, so not a 5.

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?

Three tight sentences, front-loaded with what the tool does, followed by the disambiguating when-not rule and a reference link. Every sentence earns its place with no redundancy.

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?

No output schema exists, and for a simple two-param directory creation the description covers purpose, scope, the key alternative, and behavior (recursive creation). Auth/permission requirements and error behavior on existing dirs are unstated but minor for this tool given the annotations.

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 100% and both params are documented in the schema, including the `assets/img` path example. The description adds only the domain-scoping context implied by 'in a domain's Secure Static Hosting space', so the baseline 3 for schema-heavy definitions is appropriate.

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?

Specific verb+resource+scope: creates a directory, recursively including parents, inside a domain's Secure Static Hosting space. It also distinguishes itself from the sibling tool deploy_site, which auto-creates directories, so an agent can route correctly without opening either schema.

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?

Explicit when-not guidance: 'deploy_site already auto-creates the directories in a file's path, so use this only to stand up an empty directory explicitly.' It names the alternative and the exact condition that selects this tool, leaving nothing to inference.

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