photo_downloadTrigger the Unsplash required download-tracking event for a photo by id and return the download URL; must be called before presenting the download link to users per Unsplash API guidelines.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Download tracker URL for the photo |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the description adds value by explaining the 'trigger event' behavior and the API guideline requirement. It discloses the side-effect of tracking and the return of a download URL, which goes beyond the structured annotations.
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 a single, front-loaded sentence that covers the main action, purpose, and a key requirement without unnecessary detail.
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 tool's simplicity (one parameter, rich annotations, output schema), the description is complete: it explains the trigger event, the returned URL, and the mandatory usage context. No critical gaps remain.
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 0%, but the description clarifies the only parameter 'id' is a photo ID ('for a photo by id'). Combined with the example in the schema, this is sufficient for a single simple parameter.
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 explicitly states it triggers the Unsplash download-tracking event and returns the download URL, which is a specific verb+resource+outcome. It clearly distinguishes from sibling tools like list_photos/photo by focusing on the tracking event and URL return.
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 provides explicit usage context: 'must be called before presenting the download link to users per Unsplash API guidelines.' This tells when to use it, though it does not name alternative tools or say 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.