hub_rate_limit

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

Annotations already mark it read-only, and the description adds substantial behavioral detail: it uses an unmetered HEAD request, reads specific headers, describes per-IP vs per-account metering, and explains the unlimited fallback. This goes well 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?

Every sentence in the description carries distinct, actionable information: purpose, mechanism, usage timing, auth behavior, and return contract. It is dense but well-structured with Args/Returns sections.

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?

There is no output schema, yet the description documents the exact returned dict keys and the 'unlimited' edge case. It also captures auth fallback and costing properties, so nothing an agent needs to invoke it correctly is missing.

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 leaves both parameters undescribed (0% coverage), but the Args section explains each: username/password override the corresponding environment variables. This fully compensates for the schema gap.

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?

States a specific verb ('Report') and a well-defined resource ('remaining Docker Hub pull-rate-limit budget'). This clearly distinguishes it from the many sibling tools, none of which address rate-limit budgets.

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?

Explicitly advises calling the tool 'before a large compose_pull / image_pull' to avoid hitting the cap mid-deploy. It also clarifies credential behavior and what it does not read, giving agents clear context for usage.

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