smartscale__scale_objects_from_credit_card

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

With no annotations, the description carries full burden. It explains the scaling process and optional distortion check via height, but does not disclose the output format, side effects (e.g., does it save results?), or any authentication/rate limit requirements. The description is moderately transparent.

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 concise, starting with a bracketed context tag, then a one-line summary, followed by a clear list of arguments. Every sentence is informative and there is no redundancy.

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?

Given no output schema, the description should specify return values. It does not mention what the tool returns (scaled objects?). Also, it omits prerequisites like ensuring a credit card is visible in the photo, which is especially relevant given the sibling `credit_card_photo_instructions` tool. The description is partially complete.

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%, so the description fully compensates by detailing each parameter. It explains `image_id`, `credit_card_pixel_width`, `objects` (including required and optional sub-fields), and `credit_card_pixel_height` with its distortion-check purpose. This adds significant meaning beyond the bare 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 clearly states the verb ('Scale') and resource ('object pixel dimensions using a standard CR80 credit card reference'). It distinguishes itself from sibling tools like `smartscale__credit_card_photo_instructions` by focusing on measurement scaling rather than photo capture instructions.

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?

No explicit guidance on when to use this tool versus alternatives. While it implies use after obtaining a photo with a credit card, it does not reference the sibling tool `smartscale__credit_card_photo_instructions` as a prerequisite or suggest when scaling is appropriate.

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