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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the description's real contribution is disclosing the shape of each returned record, which matters because there is no output schema. It adds no notes on ordering, pagination, or result size, which keeps it below a 5.

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?

One front-loaded sentence plus a two-word qualifier, with the field list earning its place given the absent output schema. The trailing 'Optional filter.' fragment is slightly clipped and could be folded into the main sentence without loss.

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-optional-param read-only list tool whose annotations carry the safety profile, the description covers purpose and return fields adequately. Gaps are minor: nothing about result volume/ordering or how to move from a listed form to get_form.

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 100% and the single need parameter already documents itself with examples (expired, journeyman). The description's 'Optional filter' restates the schema rather than clarifying matching behavior (substring vs. exact, which fields are searched).

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 (List) and resource (TDLR electrician forms) and even enumerates the fields returned (id, title, form number, need, PDF address). It doesn't explicitly contrast itself with the singular sibling get_form, so the agent must infer the list-vs-fetch distinction from the verb alone.

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?

'Optional filter' implies the two usage modes (list everything vs. narrow with need), but there is no explicit when-to-use statement and no mention of get_form or check_form_changed as alternatives. Usage is inferable but not guided.

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