hub_rate_limit

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description goes beyond by explaining the underlying HEAD request (unmetered), how credentials affect limits (per-account vs per-IP), fallback to environment variables, and the 'unlimited' case. No contradictions.

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 well-structured with a summary sentence followed by detailed paragraphs. While it is longer than some, every sentence adds value, and key information is front-loaded. Minor improvements could trim redundancy, but it remains clear and efficient.

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?

Despite lacking an output schema, the description explicitly lists the returned dict keys ('authenticated', 'limit', 'remaining', 'window_seconds', 'unlimited') and explains the unlimited case. It covers authentication, rate limit behavior, and edge cases thoroughly.

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 descriptions are missing (0% coverage), but the description fully compensates: it names each parameter, states they are optional, explains they override environment variables, and clarifies that the password field also accepts tokens. The effect of credentials on limit metering is also detailed.

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 opens with 'Report the caller's remaining Docker Hub pull-rate-limit budget,' which clearly states the verb (report) and the specific resource. It distinguishes itself from siblings like pull_image and compose_pull that actually consume the budget, making the tool's unique role obvious.

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 explicitly advises to 'Call it before a large compose_pull / pull_image to avoid hitting the cap mid-deploy,' providing clear when-to-use guidance. While it doesn't list exclusions or alternatives, the context is well-defined and there are no similar sibling tools for rate-limit checks.

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