hub_rate_limit

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

Annotations only declare readOnlyHint=true and destructiveHint=false. The description goes far beyond this by explaining the HEAD request mechanism, that it costs no pull budget, how credentials affect metering, the environment variable fallback, and that unlimited plans return no headers (reported as 'unlimited': true). This is rich behavioral disclosure.

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 front-loaded with the purpose and uses each sentence to convey essential behavioral details. The args and returns sections are clearly formatted and concise, with no filler or repetition.

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?

Even without an output schema, the description lists the exact return keys, explains edge cases (unlimited plans, missing headers), and covers authentication behavior. Given the tool's moderate complexity, this is complete enough for an agent to select and invoke it correctly.

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 input schema provides only parameter names and defaults, with zero descriptions. The description compensates fully by explaining that username/password are optional, override the corresponding environment variables, and that passwords/tokens are accepted. This adds critical semantic meaning.

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 a precise statement: 'Report the caller's remaining Docker Hub pull-rate-limit budget.' This names a specific verb ('report'), a specific resource (pull-rate-limit budget), and immediately distinguishes this tool from sibling hub tools like hub_tags and hub_repo_info.

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 says 'Call it before a large compose_pull / image_pull to avoid hitting the cap mid-deploy,' giving a clear when-to-use scenario. It does not provide explicit when-not-to-use guidance or name alternatives, but the context is unmistakable.

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