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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the input-output transformation and does not mention side effects, network access, error behavior, or return format. The word 'ingest' hints at reading but is not explicit about read-only safety or other operational details.

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 extremely concise (a single sentence) and front-loaded. However, it is under-specified, omitting essential details like the chunk parameter and behavioral context, so while it is brief, it sacrifices completeness for brevity.

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?

The tool has two parameters, no output schema, and no annotations, so the description must compensate. It fails to explain the chunk parameter or any nuances of handling PDFs/YouTube, making it inadequate for an agent to invoke the tool correctly without further inference.

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 description coverage is 0%, so the description must explain both parameters. It mentions 'URL/PDF/YouTube' which loosely covers the 'url' parameter, but the 'chunk' boolean parameter is completely unexplained, leaving the agent without any guidance on how to use it.

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 'Ingest URL/PDF/YouTube → markdown' clearly states the tool's action (ingest/convert) and outputs (markdown). It distinguishes from siblings like extract_url or ocr_url by explicitly listing multiple input formats and the conversion target.

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?

No guidance is provided on when to use this tool versus alternatives such as readability or html_to_markdown. The description gives no context about appropriate scenarios, exclusions, or prerequisites.

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