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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the description needn't re-litigate safety. It adds the useful fact that the result set is a fixed, small set of three profiles each carrying discovery tags, but says nothing about ordering or the tag format, which matters since there is no 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?

A single front-loaded sentence with zero filler. The fixed cardinality ('three') is the most actionable detail and appears early.

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?

With no output schema, the description is the sole source of truth about the return value, and it stops at 'profiles and their discovery tags' without saying what a tag looks like or how to use one in a later call. For a tiny discovery tool that is close to adequate, but a single clause about the shape of the response would close the gap.

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 there is nothing to disambiguate and no risk of misuse; the baseline for a parameterless tool applies. The description correctly doesn't invent arguments.

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 ('the three supported evaluation profiles and their discovery tags'), and the cardinality ('three') makes the scope concrete. It is distinguishable from the audit/referee/upload siblings, though it never bridges the name 'verticals' to 'evaluation profiles', which is the one thing an agent may wonder about.

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?

No statement of when to call this versus alternatives such as describe_referee or get_referee_usage, and no precondition or typical follow-up. The phrase 'discovery tags' weakly implies it is an entry point, but the agent must infer that.

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