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

Annotations declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is partly covered. The description adds real value beyond that: the signing is performed by the user themselves (not the agent), it requires a director/board-member role, and the correct next call is check_registration_status. Return format is conveyed ('signingUrl') even without an output schema.

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, zero filler: purpose first, then prerequisite and next step. Every clause earns its place and the key constraint (self-signing by a director) is front-loaded.

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 one-parameter tool with no output schema, the description covers the action, the returned artifact, the authorization prerequisite, and the follow-up step. The only gap is not explicitly distinguishing this from get_transfer_poa_signing_link, though the 'limited POA' phrasing makes the distinction inferable.

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?

There is a single required parameter at 100% schema description coverage, and the schema already explains that leiId is the GUID from start_lei_registration or list_my_leis. The description adds only the contextual hint that this is a 'draft LEI application', which is marginal; baseline 3 applies when the schema carries the parameter documentation.

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 names a specific verb and resource ('Returns the page where the user signs the limited POA') and even names the returned field (signingUrl). It is clearly distinguishable from the sibling get_transfer_poa_signing_link and download_limited_poa, which concern a different POA type or a download rather than a signing page.

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 states a prerequisite ('the user must be a director or board member of the entity') and an explicit follow-up ('After they have signed, call check_registration_status'), which routes the agent through the workflow. It stops short of explicitly contrasting with the transfer-POA sibling or saying when not to use it, so it is clear context without full exclusion guidance.

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