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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the trailing 'Read-only.' adds no information. The description does contribute the taxonomy's shape (two levels, bilingual labels, record counts), which sets expectations about result size and structure, but it says nothing about authorization needs or whether the catalogue is complete versus filtered.

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 payload information is front-loaded in the first sentence, and the search_solutions pointer follows logically. The closing 'Read-only.' is wasted text that only restates the annotations, but the rest is tight and free of filler.

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 a declared output schema, the description supplies what the schema cannot: what the taxonomy represents, example values, and how the returned ids feed into search_solutions. Nothing essential is missing, though a note on whether the list is exhaustive or environment-dependent would complete it.

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 zero parameters, so the schema carries no semantic burden and the baseline is 4. The description goes slightly beyond by clarifying that the ids it returns are usable as the `process` argument elsewhere, connecting the output to a sibling's parameter.

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 HODDS process taxonomy) and names the exact contents: groups, processes, English/French labels, and per-process record counts. An agent can distinguish this from siblings like search_solutions or list_gaps 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?

Explains the downstream use case directly: a process id returned here is accepted as the `process` filter of search_solutions, which tells the agent this is a discovery/lookup step in a two-tool workflow. It does not, however, name conditions for when not to call it or contrast it with other listing siblings.

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