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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: results are ordered newest first and each item includes an image_url. It does not describe pagination or empty-result behavior, but that is a minor gap for a simple read-only list 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?

The description is compact, front-loaded, and every sentence earns its place: what is listed, how it is ordered, what the items contain, and when to use it. No redundant filler exists.

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?

For a simple read-only list tool with three self-explanatory parameters and readOnly annotations, the description covers the core purpose, ordering, and a key output field. It is slightly incomplete because limit/offset are not described, but the overall context is sufficient for most agents to invoke it correctly.

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 0%, so the description must compensate for undocumented parameters. It only hints at project_id via 'in a project' and never explains limit or offset, even though their semantics are not formally defined anywhere. The parameter names are conventional, but the description does not add the needed meaning.

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 uses a specific verb ('Lists'), identifies the exact resource ('FAVORITED (hearted) photos in a project'), and adds distinguishing detail ('newest first'). It clearly separates this tool from siblings like list_assets, list_generations, and list_projects by emphasizing the favorited/liked subset.

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 states a clear use case: 'Use this to look at a project's best/liked shots.' This tells an agent when to choose it, though it does not explicitly mention alternatives or when not to use it.

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