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

The description adds useful behavior beyond annotations: it guarantees a single-record return and prescribes how the final answer must present url vs. metadata.source_url. However, the annotations declare readOnlyHint, idempotentHint, and openWorldHint all false, and the description does not address why a lookup-type tool would carry those flags or disclose any side effects, failure behavior, or not-found handling.

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 sentences with zero filler. The primary verb-resource-scope claim is front-loaded, the input requirement is the second sentence, and the output-presentation rule earns its place as a concrete agent-facing instruction. Every sentence adds value.

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 single-parameter lookup with an output schema present, the description covers the input precondition, the return cardinality, and the output formatting rule. Minor gaps remain: no mention of not-found/error behavior and no explicit route to search when the ID is unknown, but these are small against the tool's simplicity.

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 bare schema only states id is a string of 1–200 chars. The description compensates meaningfully by clarifying that the id must be an exact, stable, already-known record identifier rather than a search term or fuzzy query—real semantic content beyond the schema.

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 states a specific verb ('Retrieve'), a specific resource ('one current public BrinkerAdvisor record'), and enumerates the exact fields returned (yield, term, freshness, canonical link, provenance). The scoping condition 'when its exact stable record ID is already supplied' sharply distinguishes it from the search sibling without needing to open either schema.

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 gives clear usage context: it is for the case where an exact stable record ID is already in hand ('Requires one known ID and returns one record'), which implies search is the alternative when no ID is known. However, it never names the sibling tools explicitly nor states when-not-to-use conditions.

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