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

Annotations already cover the read-only safety profile, but the description adds genuinely useful traits beyond them: the return payload is inline MCP image attachments, and it discloses a $0.10 cost and an API key requirement. These are exactly the kind of operational facts an agent needs and cannot get from the schema.

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?

Three tight sentences, front-loaded with the core action, then return format, then cost/auth. Nothing is wasted, though the sentences are more parallel facts than a prioritized narrative.

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?

An output schema exists so return values needn't be explained, and the inline-attachment note compensates nicely. But with 6 parameters, 0 required, and half undocumented, the definition leaves the agent without enough semantic grounding to form an effective query.

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 only 50%: query, place_id, and person_ids have no descriptions. The phrase 'by query/metadata' only loosely gestures at the query param and does nothing to explain person_ids or place_id, so the description fails to compensate for the coverage gap.

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?

States a specific verb (search) and resource (person photos and entity assets) plus the retrieval mechanism (query/metadata). However it never distinguishes itself from close siblings like get_person_photos, get_photos_for_event, or get_photos_for_place, so an agent can't tell which one to pick from purpose alone.

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?

There is no when-to-use guidance or routing to alternatives. The '$0.10; API key required' note is a cost/precondition, not usage context, and it doesn't say when this general search should be preferred over the many more specific photo siblings.

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