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

Annotations already declare readOnlyHint, idempotentHint and the safe, non-openWorld profile, so the description does not need to re-establish safety. It does add one genuine behavioral rule — LEIs with a renewal already in progress are excluded — which prevents a misread of the result set, but says nothing about ordering, pagination, or empty results.

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?

A single front-loaded sentence with the return type and both filter conditions, and zero filler. Nothing could be removed without losing information.

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 zero-parameter read tool with no output schema, stating that the return is a set of LEI ids plus the two inclusion/exclusion criteria is sufficient to call and interpret it. It is only lightly thin on what an agent should do next with those ids.

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?

The tool takes no parameters, so there is no parameter semantics burden and the description cannot be faulted for gaps; baseline 4 applies. Nothing in the schema-needed sense is missing.

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?

States a specific verb and resource (returns the ids of the user's LEIs) plus a precise filter condition (due for renewal, no renewal in progress). It is distinguishable from list_my_leis by the filter, though it never names the sibling to sharpen the contrast.

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 purpose implies the usage context — checking which LEIs need a renewal order — but there is no explicit when-to-use statement, no exclusion of alternatives such as list_my_leis or get_my_lei, and no indication of what to do with the returned ids.

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