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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description does add two useful pieces beyond that: an authorization precondition ("authorized") and the exact payload subjects returned, though it says nothing about failure modes or what an unauthorized caller sees.

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 no filler and no repetition of the title. It is efficient, though the terseness borders on under-specification rather than crispness.

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 one-parameter read tool with rich annotations, the description covers the essentials of what is returned and that authorization is required. But with no output schema and an undocumented parameter, an agent still lacks enough detail about the request/response contract to call this confidently.

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% — the single parameter "briq" is documented only by a regex pattern, with no statement that it is a briq identifier or where to obtain it. The description never mentions the parameter at all, so it fails to compensate for the coverage gap.

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 gives a concrete verb ("Read") and names two return subjects (the T3 home release and the last upgrade operation), which separates it from the mutating siblings briq_upgrade and briq_up. However, "T3 home release" is unglossed internal jargon, so an agent unfamiliar with the domain cannot confidently say what a "home" or a "T3 release" is.

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?

There is no statement of when to use this versus the closely related briq_status or briq_upgrade, and no prerequisite or follow-up guidance. The agent must infer from the name alone that this is the read counterpart to the upgrade mutation.

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