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

Goes beyond the annotations by disclosing the no-disk-write guarantee, the exact return shape ({ id, path, content_type, contents, validate_with }), and the fact that from_live triggers an HTTPS probe of the public origin — a side effect the read-only/idempotent hints do not convey. It stops short of describing probe failure behavior, timeouts, or latency for that network path, which would be the remaining useful detail.

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?

Front-loaded with the core action, then scope, then return shape, then the alternative — a sensible ordering. The 12-id enumeration is long and duplicates the schema's id field verbatim, which is the one block that does not fully earn 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?

For a 9-parameter tool with one required param and no output schema, the description supplies the action, the optional network behavior, the return object's keys, and the sibling routing rule. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3; the description earns above that by tying from_live to the domain parameter and naming which discovered fields (MCP, OpenAPI, A2A, contact URLs) get pre-filled. The enumerated id list, however, merely repeats the schema's enum-like id description.

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?

States a specific verb+resource ("Generate in-memory starter boilerplate") with the full set of supported manifest ids and the explicit constraint "without writing to disk." The final sentence separates it from validate_manifest, so an agent can route between the two without opening a 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?

Explicitly prescribes when to use this tool ("to author a new manifest") and names the alternative with its own condition ("use validate_manifest to lint existing content"). It also gives the trigger for the optional live-probe path ("when from_live: true is passed with domain"), 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.