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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description adds that a brief carries a 'current quote (compose + estimated render)', which is mild extra insight into returned content. It does not, however, disclose staleness, freshness, or error behavior for a missing id, so it remains a moderate contribution.

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 tight sentence with the operation front-loaded and no wasted words. It is efficient, though the parenthetical gloss is a small extra that could be trimmed.

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 simple read-by-id tool with an output schema and annotations covering safety, the description supplies enough to call it correctly. It notes the primary content (intent + quote) without needing to restate return values the output schema already defines.

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 100% for the single parameter, so the schema already documents briefId. The phrase 'by id' merely reinforces the schema without adding format, sourcing, or validity details. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

Specific verb (Read) plus resource (brief) with a scoping qualifier ('by id'), which naturally distinguishes it from list_briefs and the create/update/delete_brief siblings. It also adds a useful gloss on what a brief contains (persisted intent + current quote). Siblings beyond the by-id/list distinction are not named explicitly, so it stays just 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?

The description is purely descriptive and gives no when-to-use condition, prerequisites, or alternatives. It never tells the agent when to reach for this over list_briefs or get_composition, or when the embedded quote is what's actually needed. Consistent with the calibration where a lack of when-to-use language earns a 2.

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