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

Beyond readOnlyHint/openWorldHint, it discloses that date strings are returned in source form with no phase, remaining-time or timezone math, that totals are never recomputed, and that a missing banner is a valid state rather than an error. The 404-on-hidden-resource behavior lives in the schema rather than the description, and the "never mutates" clause largely restates the read-only annotation, but the semantic caveats are genuinely additive.

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 purpose is front-loaded in the first clause, followed by usage example and then behavioral caveats in a logical order. The long field enumeration is somewhat plodding and partly duplicates the existing output schema, but every clause still carries information an agent would otherwise have to infer.

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 single-parameter, read-only page fetch with an output schema and annotations already in place, the description covers the missing pieces: how to obtain the path, what the returned date and total values mean, that absent banners are normal, and what the tool will not do. Nothing needed to invoke it correctly appears to be absent.

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 coverage is 100% and the schema already explains that the path must be passed unchanged, that hidden resources 404, and what each variant destination yields. The description adds the sourcing rule (take it from the jam browse response) and reinforces the overview form with a concrete slug, which is useful orientation beyond the schema text.

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?

"Read one itch.io game-jam overview page" gives a specific verb and a tightly scoped resource, and the enumeration of returned fields (path, URL, ID, title, dates, hosting links, stats, navigation) makes the output domain unmistakable. It implicitly separates itself from variants by directing the caller to the native /jam/slug overview destination rather than /entries or /results, though it never names a sibling tool outright.

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?

It states where the input comes from ("the native relative /jam/slug destination from jam browse") and gives a concrete example, so an agent knows how to source the argument. It also rules out whole classes of action ("never joins, submits, rates, comments or accesses account state"), but it does not explicitly route to alternatives like itchio_jams_entries or itchio_jams_results when a different destination is wanted.

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