Get URL Content

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

Discloses return fields (markdown, metadata), truncation behavior (truncated flag, re-request with larger max_length), and 404 for untracked URLs. This adds significant context beyond the annotations (readOnlyHint, etc.), with no contradiction.

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?

Four sentences covering purpose, usage guidance, key behaviors, and a special case (404). No unnecessary words; front-loaded with the main action.

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?

Comprehensive for a tool with 3 parameters and an output schema. Covers discovery, truncation, and error handling, leaving no gap in understanding usage and behavior.

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?

All three parameters have schema descriptions (100% coverage), and the description enhances them: suggests get_urls_report for url discovery, list_projects for project_id, and explains max_length range and truncation effect.

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 it retrieves scraped markdown content of a source URL. It references the sibling tool get_urls_report for URL discovery, distinguishing it from other tools.

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 advises using get_urls_report to discover URLs, and explains how to handle truncation by re-requesting with a larger max_length. However, it does not mention when to avoid using this tool (e.g., for chat content) or consider alternatives beyond the one sibling.

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