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

The annotations already declare a read-only, closed-world operation, and the description adds important behavior beyond that: only the top 20 are returned, there is no pagination or bulk export, and VIP access is required. It still does not describe response fields or error behavior, but the key result-limiting behavior is disclosed.

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 core action and scope, and every sentence adds a meaningful constraint: top-20 cap, filters, no pagination/export, and VIP requirement. There is no wasted wording.

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 simple read-only ranking tool with no output schema, the description covers the main call constraints: result cap, filter scope, no pagination, and VIP access. It is not fully complete because it omits return fields and leaves some ambiguity about whether month is operationally required despite the schema marking no parameters required.

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 description coverage is 0%, so the description needs to compensate. It does clarify that visa and state are optional filters and that month refers to a published month, but it provides no accepted values or format guidance for visa/state and adds little beyond the schema constraints.

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 states a specific verb/resource/metric: return the top 20 occupations by submitted EOI count, scoped to a published month and optional visa/state filters. It distinguishes this tool from broader snapshot/search tools through the top-20 ranked scope, but it does not explicitly name an alternative sibling tool.

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?

It gives useful constraints — VIP required and no pagination/bulk export — which imply this is for a capped ranking view rather than exhaustive export. However, it does not explicitly say when to use this versus siblings like get_eoi_snapshot, search_occupations, or compare_occupations.

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