URL to mind map

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context the annotations cannot: Readability extraction, dropping of navigation/boilerplate, and the hard failure mode of empty results on JS-rendered pages. It does not note network/auth constraints for fetching, but the failure-mode disclosure is the valuable part.

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 sentences, front-loaded with the core action, then extraction detail, then the failure mode and fallback. No filler; each sentence carries a distinct fact.

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?

With no output schema, the description does tell the agent what comes back (a mind-map outline, plus source text in client mode). Given eight parameters fully documented in the schema and annotations covering the safety profile, this is nearly complete; only the PDF-vs-pdf_to_mindmap overlap is left ambiguous.

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 each parameter already carries its own enum explanation, default, and range. The description adds nothing parameter-specific beyond what the schema states. Baseline 3 is appropriate when the schema does all the work.

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 and resource: fetch an http(s) page/PDF and convert its main content into a mind-map outline. It names Readability as the extraction mechanism, which tells the agent exactly what content is used. It does not, however, clarify its boundary against the pdf_to_mindmap sibling, despite explicitly advertising PDF support.

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?

Gives an explicit exclusion and a named alternative: JS-only pages will come back empty, so use text_to_mindmap instead. That is exactly the kind of routing guidance an agent needs. It does not mention when to prefer pdf_to_mindmap or export_mindmap, so the routing is partial rather than complete.

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