photos_ensure

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

With no annotations, the description carries the full burden and honestly discloses spawn, resume, settle time, injection, foreground stealing, and non-closure of sessions. Missing details like required permissions or error cases, but overall good transparency.

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 extremely concise (3 short sentences) with front-loaded action. Every sentence adds value, no redundancy.

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?

Covers main action and side effects but omits return behavior, error conditions, prerequisites (e.g., device state, app existence). Adequate but not fully informative.

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 50% (only settleMs described as 'Default 4000'). The description echoes the settle time but adds no meaning for 'udid'. It insufficiently compensates for the missing param documentation.

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: spawn/resume Photos.app, settle, inject agent. It also notes what it does not do (close TikTok) and a side effect (steal foreground), making the purpose distinct from sibling tools.

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 usage context (setup step, not closing sessions) but lacks explicit when-to-use, when-not-to-use, or direct comparison with alternatives like photos_import or photos_list.

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