search_photos

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

Annotations indicate readOnlyHint=false, suggesting the tool modifies state (opens an app). The description mentions 'Open Photos' which aligns with a state change, but does not elaborate on side effects (e.g., does it close other apps? Does it affect the current focus?). Minimal behavioral disclosure beyond what annotations imply.

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 (6 words), but brevity comes at the cost of completeness. It is front-loaded but fails to earn its place by omitting essential details about behavior and return values.

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 simple schema (1 string parameter) and no output schema, the description should clarify what the tool returns and any behavioral nuances. It does not mention whether the search yields results or just opens the app. Incomplete for an agent to confidently invoke the tool.

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 single 'query' parameter is described as 'search for a term', which maps directly to the parameter name and provides basic meaning. However, with 0% schema coverage, the description adds only minimal value—no format constraints, examples, or special instructions for the query string.

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 'Open Photos and search for a term' indicates the tool launches the Photos app and performs a search, but it's unclear if it returns results or just executes the search. The verb+resource is clear enough, but the scope (what is returned) is ambiguous. Distinguishes from siblings by being Photos-specific.

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?

No guidance on when to use this tool versus alternatives like search_google or search_youtube. No prerequisites or conditions mentioned. The agent must infer usage solely from the tool name and brief description.

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