Project documentation site

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

Annotations already flag this as potentially destructive (readOnlyHint=false, destructiveHint=true). The description adds the concrete behavior of writing multiple files into out_dir and conditionally generating thumbnails, but it does not clarify whether existing files in out_dir are overwritten or deleted, which is a notable gap given the destructive hint.

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, no filler. The first sentence efficiently packs the purpose and file inventory; the second contrasts with a sibling. Every word earns its place.

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 description enumerates all generated files and their contents, the conditional thumbnails, and the output directory. It doesn't discuss overwrite behavior or prerequisites, but for a documentation writer, the key details are present. Output schema absence is mitigated by the detailed package structure description.

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?

All 5 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds meaning by explaining that include_thumbnails triggers PNG generation linked from gallery.md, and that all files are written into out_dir, going slightly beyond the schema's property descriptions.

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 it 'compose[s] a one-folder handoff/portfolio documentation PACKAGE for a network' and enumerates the outputs (README.md, topology.md, thumbnails). It also explicitly contrasts with sibling generate_readme, making the tool's scope unambiguous.

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?

Names generate_readme as the alternative and explains the difference ('a single file' vs 'a small multi-file site folder'), with an explicit use case: 'for sharing or archiving a project.' This gives the agent a clear selection criterion.

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