Doucebeads · Image to Bead Pattern

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

Goes well beyond the annotations by disclosing that the image is sent to an external service (Doucebeads) for the request and never persisted, and by stating hard input caps of 750KB and 1 megapixel that appear nowhere in the schema. The readOnly/openWorld/idempotent hints are consistent with this - a network read that produces a downloadable artifact without stored state - so there is no contradiction.

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?

Front-loads the conversion outcome and the differentiator in the first sentence, then packages constraints, privacy and result-ordering in tight sequential sentences. A couple of clauses (the Q-version upselling instruction) read as commercial steering rather than tool semantics, but nothing is redundant.

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 six-parameter conversion tool with no output schema, the description covers input sourcing, size limits, privacy handling and the shape of the result (chart plus PNG and CSV). The remaining gap is that width/colors/max_beads behaviour - how chart size and palette reduction interact - is undocumented in both schema and description.

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 50% (brand, colors and max_beads have no descriptions), and the description compensates on the image-source axis: base64 versus URL, no local paths, and the 750KB/1MP limits that constrain image_base64/image_url. It adds little on the tuning parameters (width, colors, max_beads), which remain inferable only from their names and bounds.

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 ('Convert a user-provided PNG/JPEG into an editable fuse-bead chart') plus concrete outputs (MARD color codes, bead counts, PNG, CSV). It also explicitly positions itself against a neighbouring capability ('not AI chibi stylization'), so an agent can tell what this tool is and is not without opening the schema.

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?

Gives actionable when/how guidance: prefer base64 when the client can pass an attachment, never invent file URLs, only process user-authorized images, return the free result before mentioning the Q-version link. It does not route to the actual siblings (get_conversion_guide, lookup_bead_color), so the alternative-selection guidance is incomplete.

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

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely non-redundant behavioral fact: no image is uploaded during this call, which is a privacy guarantee not encoded in annotations.

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?

Two short sentences, content listed up front and the privacy caveat placed last as a qualifier. No filler or repetition of the title.

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 no output schema, the description carries the burden of describing what comes back, and it does so by enumerating the guide's contents. It stops short of describing structure or format of those links/limits, but is sufficient for an agent to decide to call it.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it does not waste words restating an empty 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 enumerates concretely what the guide covers: supported image formats, privacy, request limits, and printing/styling links. The closing sentence 'No image is uploaded by this call' distinguishes it from the sibling convert_image_to_pattern, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is a reference/informational lookup to consult before converting, but the description never states when to call it versus convert_image_to_pattern or lookup_bead_color, and gives no exclusions.

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

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds genuine value by warning that RGB values are community approximations rather than calibrated measurements, but says nothing about not-found handling or what fields are returned.

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 compact sentence front-loads the action and appends the data-quality caveat, with no filler. The caveat is separated by a semicolon, which keeps the primary purpose first.

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 no output schema, the description hints that RGB data is returned but does not enumerate the response fields or clarify what the lookup yields for a given code. Adequate for a simple lookup, but leaves the caller guessing about the return shape and the brand parameter's effect.

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 burden, yet it never explains the 'brand' parameter (enum mard/mard221) or the code format constraints (1-8 characters). An agent must infer the role of the second parameter entirely from the schema enum.

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 ('Look up') and resource ('a specific MARD bead code'), so the operation is unmistakable. It does not name or differentiate from the siblings convert_image_to_pattern and get_conversion_guide, though those are clearly different operations.

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?

There is no guidance on when to use this versus the sibling tools, and no note on prerequisites or what happens when a code is not found. Usage is only implied by the verb 'look up'.

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