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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral details such as ignoring anchors and returning the whole page, plus the version defaulting behavior, which goes beyond just safety.

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 well-structured and front-loaded: it begins with the core action, then usage context, then details about page content and return value, and finally clear exclusions. It is concise but informative, with no fluff or 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?

Given the schema covers all parameters and there is no output schema, the description provides sufficient context: it mentions the returned fields (title, URL, version, markdown) and clearly scopes the tool to Ionic docs only. It also supplies enough guidance to avoid misuse.

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?

The input schema already provides thorough descriptions for both parameters, including examples for URL formats, the anchor caveat, version defaults, and matching to package.json. The main description adds no extra semantic value beyond what the schema already covers.

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 the tool reads a full documentation page from the official Ionic Framework docs, specifying the verb 'Read' and the resource. It also distinguishes itself from siblings by explicitly positioning it after search_docs and warning against using it for finding pages.

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?

The description gives explicit when-to-use guidance: use after search_docs to read a page end-to-end before writing markup, and do not use it to find a page because it requires an exact URL. It also excludes Capacitor and external docs, making the intended usage unambiguous.

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