Log in to Unsplash+

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

It discloses that it opens a dedicated Chrome profile and uses credentials from pass, but does not mention side effects on existing authentication sessions or that it may skip login if already authenticated. With no annotations provided, the description carries the full burden but falls short of explaining the consequences of running this 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 a single sentence that is front-loaded with the action ('Open the dedicated Chrome profile'). It contains no filler or redundant information, making it optimally concise.

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?

The tool is simple with one optional boolean and no output schema, so the description doesn't need to explain return values. However, it does not mention expected outcomes or prerequisites like pass being installed, which leaves a small gap for complete understanding.

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 schema fully describes the force parameter with 100% coverage, so the baseline is 3. The description adds no extra parameter information, but this is acceptable given the schema's completeness.

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 signs in to Unsplash+ using a dedicated Chrome profile and credentials from pass. This is a specific verb+resource combination that distinguishes it from sibling tools like unsplash_plus_logout or unsplash_plus_status.

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 the tool is used when login is needed, but does not explicitly mention when to use alternatives like unsplash_plus_continue_login. It also lacks guidance on prerequisites such as pass being configured or when to set the force parameter.

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