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

With no annotations, the description carries the transparency burden. It adds useful context by stating 'public URL' (implying non-public will fail) and 'clean markdown' (output format), plus the cost in sats. However, it does not disclose behavior on failures, dynamic content, or rate limits, which would be valuable for a scrape tool.

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 a single sentence with an additional cost note, achieving maximum conciseness. The essential information (action, target, output, pricing) is front-loaded and every word earns its place.

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?

For a simple one-parameter tool with no output schema and no annotations, the description covers the core functionality, output format, and cost. It does not mention error cases or limitations beyond 'public', but given the low complexity, the level of detail is sufficient.

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 describes the 'url' parameter as 'URL to scrape', giving 100% coverage. The description adds the qualifier 'public' but does not elaborate on parameter format or constraints, so it adds minimal value beyond the schema.

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 explicitly states the verb 'Scrape', the resource 'any public URL', and the output 'clean markdown'. This clearly distinguishes it from sibling tools like verity_search or verity_sentiment, which have different purposes.

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 implies usage for extracting markdown from a public URL, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The context is clear enough for a distinct function but lacks direct guidance.

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