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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a key behavioral trait (ordering: 'most dangerous first') as well as the scope of items included (lapsed or missing insurance), which is useful. However, it does not mention whether the tool will also return sorted-by-danger or any other read-only guarantee, return format, or whether the data is live. The description is acceptable but not rich enough to carry the full burden with no annotations.

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 description is one sentence with a front-loaded verb and resource, followed by a single, purposeful clause about ordering. Every word earns its place—it identifies the subject, defines the selection criteria, and highlights the output ordering. No filler, no repetition of the tool name.

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-only list tool without an output schema, the description captures the essential behavior: what is listed and the ordering. It does not describe the response shape or limits, but the simplicity of the operation makes that less critical. It might benefit from a brief note on whether 'lapsed' means expired in the insurance context, but it is otherwise sufficient for an agent to call it correctly.

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 has zero parameters, so the baseline is 4. The description adds no parameter-specific semantics (there are none to document), but it reinforces the conceptual basis that the tool is a self-contained listing operation with no inputs. No additional parameter clarification is necessary.

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 a specific verb ('list') and resource ('subcontractors with lapsed or missing insurance documents'), and adds a clear scoping criterion ('the ones creating liability exposure right now') that distinguishes it from siblings like get_expiring_cover or get_compliance_summary. The ordering ('most dangerous first') adds further precision. An agent can distinguish this tool from its siblings without inspecting the schema.

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 implies a usage context — when you need to see subcontractors that currently pose liability risk — but does not explicitly name alternative tools or provide when-not-to-use guidance. It clearly telegraphs that this is for identifying immediate exposure, which is helpful, but it leaves the distinction from get_expiring_cover to be inferred. This is clear context without explicit exclusions, so 4 rather than 5.

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