Preview a local business profile

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

Adds useful behavior beyond the annotations: no Google contact/publishing, config text is preserved in the output file, optional photos are re-encoded, and a local browser is required. It does not cover overwrite behavior or permission expectations, but the annotations already establish the local, non-destructive write profile.

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 core action and output format, then adds only meaningful constraints: local photo handling, no Google contact, config retention, and browser requirement. No sentence 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?

No output schema exists, but the description sufficiently explains that the result is an SVG/PNG written to output_path and emphasizes local-only behavior. Minor gaps remain around scale behavior and whether output_path is overwritten.

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 60%, with descriptions for the three path parameters but not for scale or format. The description reinforces local JSON config input, optional photo re-encoding, and SVG/PNG output, but leaves scale semantics to the 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?

States a specific verb and resource: "Render an illustrative business listing preview" from a local JSON configuration into SVG or PNG. The business-listing preview focus and local-config input distinguish it from the file/image/PDF utility siblings.

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?

Clearly frames the use case as an illustrative local preview and explicitly excludes contacting/publishing to Google or verifying a real listing. It also notes the local browser requirement, though it does not call out an alternative sibling tool.

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