ClockNext: read a docs page

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

With no annotations provided, the description carries the full burden. It clearly indicates this is a read operation, returns authoritative page content 'verbatim', and explicitly warns that external fetches may 'silently drop details.' It doesn't mention errors or rate limits, but for a read-only docs tool, the key behaviors are well disclosed.

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 front-loaded with the core purpose, and each paragraph adds useful guidance. It is longer than strictly necessary, with some repetition (e.g., 'read the whole page' and 'read THAT page in full'), but every sentence contributes to clarity and safe usage.

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 tool's simplicity (one required parameter) and the absence of an output schema, the description fully compensates by specifying the Markdown return format, the type of content included, and how to obtain the input. It is complete for the intended workflow.

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 schema already covers the single `path` parameter (100% coverage), but the description adds important semantics by explaining the parameter comes from a clocknext_search_docs result and providing valid example values like 'https://help.clocknext.com/docs/sdk/signals'.

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's function: 'Read the FULL contents of a single ClockNext docs page as Markdown.' It identifies the specific resource (docs page) and action (read) and explicitly distinguishes itself from its sibling clocknext_search_docs, which only returns snippets.

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 this right after clocknext_search_docs: pass the url of a promising search result.' It also names the alternative to avoid (external web-fetch/browser tools) and explains why, making the usage decision clear.

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