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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about authentication requirements (the access_token parameter implies a subscriber token is mandatory), pagination behavior via limit, result volume, or what shape the response takes. For a lookup endpoint that may return large result sets, the absence of any operational context is a real gap.

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?

It is short and front-loads the resource, but it is written as fragments rather than a complete sentence, and the cryptic "PRO." prefix consumes space without communicating anything to an unfamiliar agent. Conciseness is achieved through omission rather than economy.

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?

With no annotations, no output schema, and three parameters of which two are undocumented, the definition is under-specified for the calling agent. Missing are the auth requirement, the default/limit semantics, and any indication of what an entry contains — all of which the description would need to supply here.

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 only 33%, and the description addresses only the required `program` parameter — but it does so valuably, supplying four real program code formats that the bare `{"type": "string"}` schema does not convey. The `limit` parameter is never explained, and the auth parameter's meaning is left entirely to the schema description.

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 identifies the resource (SDN entries) and the filtering key (sanctions program code), reinforced by concrete code examples like RUSSIA-EO14024 and SDGT. However, the leading fragment "PRO." is an unexplained abbreviation, and no verb is stated — the listing action is only inferable from the tool name. It does not distinguish itself from siblings ofac_check and batch_screen, which an agent could easily confuse with a program lookup.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the sibling tools that perform screening (ofac_check, batch_screen) versus this lookup-by-program. An agent must infer from the name alone that this enumerates entities by list code rather than screening a specific name.

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