get_picture

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

No annotations are provided, so the description must fully disclose behavior. It states the output is a PNG binary, but does not mention error handling, permissions, path resolution, or any side effects. The tool is likely a read operation, but this is not stated. Minimal behavioral disclosure beyond the basic action.

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 sentence that directly conveys the purpose and required inputs. There is no redundancy or extraneous information. It is appropriately sized for the tool's simplicity.

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 description adequately covers the core function and input for a simple retrieval tool, but with no annotations or output schema, it lacks details on response format (e.g., binary vs base64), error conditions, or constraints. It is minimally complete but leaves some ambiguity.

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 schema provides no descriptions for the two string parameters, and the description only says they are used to specify the location. It does not clarify what the subfolder is relative to, or any expected format. This adds minimal value beyond the parameter names themselves.

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 tool's function: to retrieve a PNG binary by specifying a subfolder and filename. This distinguishes it from sibling tools like generate_picture (which creates) and the caption/tag tools (which analyze metadata). The verb '取得する' (retrieve) is specific and unambiguous.

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 implies the tool is for retrieving existing images, which distinguishes it from generate_picture. However, it does not explicitly mention alternative tools or provide exclusionary guidance. The context is clear but lacks explicit 'when/not' instruction.

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