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

Annotations already declare a safe read-only, closed-world operation, and the description adds substantial context beyond them: empty-list vs not_found semantics, no auth or cost, a concrete rate limit (20/min per IP) with the resulting rate_limited error, and a data source. This is exactly the extra behavioral detail the agent cannot infer from 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?

The purpose and the routing guidance are front-loaded, and the trailing sentences each deliver a distinct operational fact (empty vs not_found, cost/auth, rate limit, disclaimer, source). No sentence is filler despite the density.

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?

An output schema exists, so return-value shape needn't be documented, and the description still covers the two edge outcomes an agent must handle (empty list vs not_found). Combined with the rate-limit and auth notes, nothing needed to call this tool 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?

Schema coverage is 100% and the single 'month' parameter already carries the YYYY-MM pattern, an example, and the not_found caveat. The description restates the not_found behavior but adds no new syntax or format meaning, so the baseline 3 for schema-complete parameters applies.

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?

Opens with a specific verb and resource ('Returns every lettered advisory note in a month's Visa Bulletin') and immediately illustrates the content with a concrete example ('EB-1 India may become unavailable'). It explicitly distinguishes itself from the sibling chart tools get_visa_bulletin and get_visa_bulletin_dv.

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?

Gives an explicit trigger ('when the user asks whether dates are expected to advance, hold, or retrogress') and names the alternatives plus the condition that selects them ('For the chart dates themselves, use get_visa_bulletin or get_visa_bulletin_dv'). Both when-to-use and when-not-to-use are covered.

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