reach_read

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

With no annotations, the description discloses automatic routing, degradation, and meta.setup_hint. Does not cover auth or error handling, but provides substantial behavioral context.

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 main purpose, followed by platform list and degradation. Efficiently structured with no wasted sentences, though it could be slightly more concise.

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 complexity (multiple routing, stock tickers, degradation) and no output schema, the description covers key behaviors. Missing details on return format but sufficient for an agent.

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 has 0% description coverage. Description adds meaning for the 'url' parameter (accepts stock tickers) but does not explain 'max_chars' beyond its default. Partially compensates for missing schema 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?

Explicitly states 'Read any URL as clean text/Markdown' and lists specific platform routings (YouTube, GitHub, etc.), distinguishing it from siblings like reach_search which is for searching.

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?

Implicitly tells when to use (when you have a URL to read) and notes degradation behavior. Does not explicitly state when not to use or alternatives, but context is clear.

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