from_site_url

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

With no annotations, the description carries the full burden and does disclose several important traits: legacy links are accepted, the clipboard-JSON format is accepted, and unrecognized parameters surface in an `unresolved` field. It does not say what happens on a malformed URL or whether any network fetch occurs, but disclosure is well above the annotation-less baseline.

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?

Three short sentences, front-loaded with what the tool does and what it returns; the inline URL example and legacy/clipboard caveats each carry real information. The truncated example URL is a little noisy but still illustrative rather than wasteful.

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 parsing tool with no output schema and no annotations, the description covers input formats, the returned structure, and the `unresolved` field, which is enough for an agent to call it correctly. Error handling for invalid input is the only notable omission.

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 0% (the lone `url` parameter is undocumented), so the description must compensate, and it largely does by explaining the two accepted input formats with a concrete URL example. It is slightly ambiguous whether the exported JSON is passed through the same `url` parameter, leaving a small gap.

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 ("Reads a link from the LPC generator site") plus the exact output shape ({body_type, items}) and names generate_character as the consumer. It never explicitly contrasts itself with the inverse sibling to_site_url, so the differentiation is inferred from context rather than stated.

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 trigger conditions are clear: use it when you have a link from the LPC generator site or JSON from the site's Export to Clipboard button, and the result is "ready for generate_character". There is no explicit "when not to use this" or routing to an alternative tool, so it stops short of a 5.

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