photographi_analyze_photo

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It describes the fast_mode parameter's trade-off between speed and forensic precision, which is a key behavioral aspect. However, it does not mention any other side effects (e.g., file modification) or prerequisites, though the tool appears to be read-only. The description is fairly transparent but could be more explicit about non-destructive behavior.

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 two sentences long. The first covers purpose and output, the second provides usage guidance and sibling differentiation. Every sentence is essential; no unnecessary words.

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 the detailed input schema (5 parameters with descriptions, enums, defaults) and the presence of an output schema, the description is complete. It explains the tool's purpose, what it returns, and when to use it versus the sibling tool. No additional information is needed for successful tool invocation.

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 high (80%), so baseline is 3. The description adds no additional parameter-level detail beyond what the schema already provides (e.g., metrics list, fast_mode behavior). It does summarize the overall output, which is helpful but not specific to parameter semantics. Thus, the description adds minimal value beyond 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?

The description clearly states the tool analyzes a single photo for technical quality metrics like sharpness, exposure, noise, etc., and returns an overall score, judgement, and per-metric breakdowns. It distinguishes itself from the sibling batch tool 'photographi_analyze_folder' by explicitly noting it is for individual images.

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 explicitly says 'Use this for detailed inspection of individual images' and provides the alternative 'For batch analysis, use photographi_analyze_folder.' This gives clear when-to-use and when-not-to-use guidance.

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