r-pic

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

With no annotations provided, the description carries the full disclosure burden and handles it well: it reveals that the image is sent to an external vision model (with cost/privacy implications), lists accepted formats, and documents default behavior including environment-var fallbacks (VISION_PROVIDER→dots, VISION_MODEL→dots3-note-prev). It stops short of disclosing error handling for missing/invalid paths or file-size limits.

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 one-line functional summary is front-loaded, followed by a scannable line-per-parameter list with no filler. Every line earns its place given the schema's 0% description coverage.

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?

All invocation-critical information is present: path requirement, question semantics, provider/model selection with env fallbacks, and the max_tokens cap. The output is described as text and an output schema exists, so return-value detail is unnecessary; the main gap is edge-case behavior such as handling of nonexistent paths or unsupported formats.

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%, and the description fully compensates: all 5 parameters are documented with meaning, requiredness, valid values (provider: openai/dots; model: dots3-note-prev), and defaults. Notably it explains that null schema defaults resolve via environment variables, a behavior the schema itself cannot express.

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 states a specific verb and resource (识别本地图片 — recognize local images), lists supported formats (PNG/JPG/WEBP/GIF), and names the outcome (text description or Q&A result). It is clear and self-contained, but it never explicitly contrasts with sibling tools like r-vid, g-pic, or b-gen, so an agent must infer the distinction from the '本地' (local) qualifier and the r- recognition prefix.

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 usage context is implied by the scoping: this is for local image files of specific formats, producing text output, so an agent can infer it fits tasks like 'describe this image file.' However, the description offers no explicit when-to-use/when-not-to-use framing and never mentions alternatives, which is a real gap given five sibling tools of ambiguous function.

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