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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: results are "anonymised server-side," which tells the agent not to expect identity data in the payload. It stops short of 5 by not covering pagination or result ordering.

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 tight sentences: the returned sets are front-loaded, then the privacy note, then the filter options. Every sentence carries information; only the slightly elliptical phrasing of the filter sentence costs it a point.

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 only two optional parameters and no output schema, the description covers the substantive questions: what sets are returned, what fields appear, and that data is anonymised. Missing are pagination/volume expectations and the no-filter default, which are relevant for a list tool but minor.

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 0%, so the description must carry the load — and it does map the prose to the status enum values (open = "looking for a team," vetting, executed = "archive of delivered projects"). It also explains what `tangible` selects. It does not state the default behavior when no status is passed, but the enumeration implies all three sets.

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 resource (public briefs) and enumerates the three record sets it returns: open briefs seeking a team, vetting-stage ones, and delivered-project archive. It also names the fields carried (budget, sector, delivery team). It doesn't explicitly differentiate from the nearest siblings read_brief and read_pitchable_briefs, so it stops short of a 5.

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?

"Filter by status or to tangible-world projects only" implies how to narrow results, but there is no explicit when-to-use guidance and no routing away from read_brief or read_pitchable_briefs. The agent must infer that this is the browse/discovery tool versus the single-record read tools.

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