photographi_get_scene_content

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

No annotations provided, so description bears full burden. Describes detection and return of labels, implying read-only behavior. Lacks explicit statement about no side effects, but adequately clear for a detection tool.

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?

Two efficient sentences plus a one-sentence alternative mention. No fluff; main purpose and usage guidance front-loaded.

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?

Simple detection tool with one parameter and output schema provided. Description fully covers purpose, usage, and alternative. No missing context.

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 covers 100% of parameters with clear detail ('Absolute path to RAW/JPEG/TIFF.'). Tool description adds no extra parameter information beyond schema, meeting baseline for high coverage.

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?

Clearly states it detects objects using YOLO and returns object labels. Distinguishes from sibling tool 'photographi_analyze_photo' by contrasting quick indexing vs. full analysis.

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?

Explicitly recommends use 'for quick scene indexing or content-based search' and directs to 'photographi_analyze_photo' for alternative cases. Clear when and when not to use.

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