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

With no annotations, the description carries the full burden and does reasonably well: it discloses the authentication requirement ('Needs an API key'), the exact resource returned, and clarifies this is informational rather than a decision. It is implicitly a read-only listing. It omits rate limits, caching, or error behavior, 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?

Three short sentences: the question the tool answers, the payload it returns, then the prerequisite and the alternative. Zero filler, and the routing hint ('use decide') is placed last where it belongs.

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 metadata tool with no output schema and no annotations, the description covers what is returned, what auth is needed, and how it differs from the decision tool. The unresolved name-vs-content mismatch ('use_cases' vs ranking profiles) is the only thing that keeps it from being fully complete.

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 and the input schema is empty, so there is no parameter semantics to document. Per the rubric, 0 params establishes a baseline of 4; nothing in the description conflicts with this.

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 opens with a concrete question and states exactly what is returned: 'the profiles, the evidence floors and the neutrality commitment' from a named JSON resource. It distinguishes itself from the sibling 'decide'. The one gap is that the tool name 'list_use_cases' does not match the described content (ranking profiles/policy), which leaves a small ambiguity about scope.

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?

It gives an explicit exclusion and an alternative: 'Not a decision: use decide for that', routing the agent away from the decision-making sibling. It also states the prerequisite 'Needs an API key'. It does not address the other siblings (rank, policy_check, model_info), but the key routing decision is covered.

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