ov_check_auth

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the two possible states and the concrete rate limits attached to the anonymous mode, which is real value. However, it does not state that the call is side-effect-free/read-only, nor what the response looks like (flag? message?), leaving the outcome shape to inference.

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?

A single sentence, front-loaded with the verb and subject, with the rate-limit detail placed as a parenthetical clarification. No filler or redundancy. Size is well matched to the tool's simplicity.

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 zero-parameter diagnostic with no annotations and no output schema, the description conveys what is being probed and the practical meaning of each outcome (rate-limit tiers). Only the exact return format and the recommended next step when unauthenticated are missing, which is a minor gap at this complexity level.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter hints are present.

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 names a specific check ('whether Openverse API credentials are configured') and pairs it with the observable consequence: authenticated rate limits versus anonymous '20/min + 200/day'. A reader knows exactly what the tool reports. It stops short of naming a sibling to contrast with (e.g. ov_login / ov_register), so it is clear but not fully differentiated.

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?

Usage is only implied: the mention of credentials and rate limits suggests calling it before or when hitting throttling, but there is no explicit 'use this when...' or 'do not use for...' guidance. No prerequisites or follow-up actions (e.g. call ov_login if unconfigured) are stated.

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