ov_login

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

No annotations are provided, so the description carries the full burden, and it meets most of that burden. The description discloses that the credentials are persisted, that the exchange is validated immediately, and that anonymous access remains available. It is missing details on where credentials are stored, whether they overwrite prior ones, and what happens on invalid input, which prevents a 5.

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?

It is written in three dense sentences that each add value: what the tool does, the rate-limit payoff, the prerequisite URL, and the fallback behavior. The information is front-loaded, with no filler.

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 two-parameter tool with no output schema, the description covers the essential context: the purpose, the rate limits, the prerequisite, and the fact that the credentials are verified. The only gap is that it does not describe the failure mode for invalid credentials, which keeps it from a 5.

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 100%, and both parameters are already documented as the Openverse client_id and client_secret. The description adds nothing parameter-specific beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Save Openverse API credentials (OAuth2 client_id/client_secret)', and it quantifies the benefit (rate limits from 20/min + 200/day to 100/min + 10,000/day), so the agent knows exactly what the tool does. It does not explicitly differentiate itself from the closely related siblings ov_register and ov_check_auth, which keeps it from a 5.

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?

It states clearly when to use the tool: when you want higher rate limits, and it names the prerequisite (register an app at https://api.openverse.org/v1/). It also says the tool is optional because 'anonymous access keeps working without this'. It could go further by pointing to ov_check_auth or ov_register, but the usage context for this tool alone is clear.

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