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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real domain context beyond them: this is the public catalogue, and it includes the acceptance threshold that decides whether a brief publishes. The main gap is that it doesn't describe the return shape or ordering, which matters slightly since there's 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 that packs the resource, its fields and the downstream consequence of the threshold without a wasted clause.

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, no-output-schema tool, the description covers enough: it tells the agent what the returned catalogue contains and why it exists. It could add a brief note on shape/ordering or a nudge to use it before publishing, but nothing needed to call it correctly is missing.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies; the description correctly says nothing about 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?

The description names a specific resource (the rule catalogue a brief is scored against) and enumerates its contents: ids, labels, weights and the acceptance threshold. It is clearly distinguishable from every sibling, which read briefs, pitches, bookings, teams or profiles rather than scoring rules, though it doesn't say so explicitly.

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?

Usage is only implied: an agent can infer this is what you call to learn the scoring criteria before drafting or publishing a brief, but no when-to-use, when-not-to-use, or alternative (e.g. propose_brief_draft, read_brief) is named.

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