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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does add one meaningful behavior — images being re-inlined — but it omits important behavioral traits such as the credit-billing requirement tied to npub, version selection via ref, and any auth/dpop expectations.

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, front-loaded sentence with no filler. It states the action and the key transformation in a compact way, which is exactly what conciseness should look like.

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 presence of an output schema and reasonably detailed parameter descriptions makes the tool invocable, but the description is too thin on its own to fully prepare an agent. Missing context includes when to use versioned fetches vs latest, the billing side effect tied to npub, and how this differs from a plain list result.

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 description adds no parameter-level meaning, but the schema already covers most parameters with descriptions for design_id, ref, and npub, yielding roughly 75% coverage. The dpop_token remains effectively undocumented, so the description does not need to do all the work, but it also does not compensate for that 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?

The description uses a specific verb ('Fetch') and resource ('one of your stored designs'), and the phrase 'in full, with its images re-inlined' clearly differentiates this from list-oriented siblings like roastify_list_designs. It is concrete and not a tautology of the tool name.

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 provides no guidance on when to choose this tool over alternatives such as roastify_list_designs or roastify_list_design_versions. It also does not state prerequisites like needing a design id or owning the design. Usage context must be inferred entirely from the name and schema.

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