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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds genuinely new traits: output is converted to markdown by default, raw HTML is available via as_markdown=false, output is truncated at max_chars, and the call costs no credits ('Free'). It doesn't say whether truncation is signalled in the response or how long artifacts persist.

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?

A single dense sentence that front-loads the action and its identifier, with parameter behavior packed into a parenthetical rather than scattered. The clipped relative clause 'a page get_crawl or fetch_url lists' and the trailing one-word 'Free.' are slightly awkward, but nothing is padding.

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?

With annotations covering safety and an output schema covering the return shape, the description only needs to cover provenance, format switching, and truncation — all of which it does. Artifact lifetime/expiry and whether truncation is reported back are the remaining gaps, minor for a read-only tool.

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 carry the full load — and it explains the two optional parameters in usable terms: as_markdown toggles markdown vs raw HTML, max_chars is the truncation cap. artifact_id is only covered as 'by its id', leaving its format/source-of-truth implicit, which keeps it short of a 5.

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?

States a specific verb and resource ('Read a stored artifact of the account by its id') and grounds it in concrete provenance — artifacts produced by get_crawl or fetch_url — which distinguishes it from the fetching siblings. The parenthetical about HTML-to-markdown conversion tells the agent exactly what comes back.

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 phrase 'such as a page get_crawl or fetch_url lists' makes it clear this is the follow-up call once you hold an artifact id, which is strong contextual routing. It stops short of an explicit exclusion (e.g., 'use fetch_url for fresh fetches'), so it lands below the top score.

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