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

Annotations already declare readOnlyHint=true and destructiveHint=false DNA. The description reinforces this with 'Lists ... with status' and adds useful behavioral guidance ('never ask them for an application id'). It doesn't mention pagination or response shape, but the read-only, no-side-effect behavior is well covered.

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?

Two short sentences with zero waste. The first sentence states the operation and the second gives a critical behavioral directive (call first, don't ask for an ID).

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 list tool with a single required parameter, the description covers the entry-point behavior and the key constraint (don't ask for an application id). Siblings like itin_get_itin_application clarify the complement. The output schema would describe the returned statuses, so nothing critical 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% for the single required parameter (companyId as a UUID object), so the schema carries the burden. The description adds no parameter-level detail beyond the tool's overall purpose, which is acceptable but not additive. Baseline 3 is appropriate.

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 action (list ITIN applications), a clear resource (company ITIN applications), and an output signal (status). It also differentiates the tool from siblings like itin_get_itin_application by clarifying this is the list entry point, not a single-record fetch.

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 gives an explicit sequencing instruction: call this first and never ask the user for an application id. It stops short of naming the alternative tool (itin_get_itin_application) directly, but the guidance is still clear and actionable.

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