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

No annotations are provided, so the description carries the full disclosure burden. It usefully mentions a result cap ('Up to 100'), but does not explain authentication requirements, read-only behavior, rate limits, error handling, or whether the operation consumes subscriber quota.

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 sentence is short, but it is under-specified rather than efficiently concise. The leading 'PRO.' token is unexplained and does not help an agent understand or invoke the tool.

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 and no output schema, the description should carry more context. It does not explain authentication, result structure, pagination, or how this differs from the sibling screening tools, leaving significant gaps for an agent.

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 only 50%, but the description partially compensates by clarifying that the required query parameter represents a name or keyword. The access_token parameter is undocumented in the description, though its schema entry does describe it as a subscriber token.

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 that the tool returns DFAT sanction matches for a name or keyword, which gives a recognizable resource and result type. However, it lacks an explicit verb, never explains what 'PRO' means, and does not distinguish the tool from sibling tools like screen_name or batch_screen.

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 guidance about when to use this tool versus batch_screen or screen_name, nor any prerequisites or exclusion criteria. The only contextual hint is the implicit use case of looking up matches for a single name/keyword.

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