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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: a Bearer token is required, and the exact fields returned. It does not state that the call is read-only/non-mutating, nor anything about failure modes (expired token, missing auth) or rate limits. Adequate but not rich.

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?

One compact sentence with the returned data front-loaded and the auth requirement trailing, which is the right order. The field list is terse noun fragments rather than full clauses, but nothing is wasted or repeated.

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, non-mutating read with no output schema, the description supplies what an agent otherwise lacks: the shape of the returned data and the auth requirement. Only error behavior and the read-only nature are left unstated, which is a minor gap at this complexity level.

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, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a no-argument call by mentioning only an auth header rather than any input fields.

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?

Names the resource (Bridge Stack account) and enumerates the fields returned (tier, expiry, provider spend, spend cap), so an agent knows exactly what data it yields. It reads as a status/read tool without an explicit verb, and it does not reference the siblings bridge_promotion_verdict or bridge_scoreboard, but those serve clearly different purposes so confusion is unlikely.

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 would call this to check account tier or spend state. There is no explicit when-to-use or when-not, and no alternatives named. The one concrete guidance given is the auth prerequisite ("Requires your Bearer token"), which is useful but not a usage rule.

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