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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that no price is embedded in the server and that absent manifest values stay absent rather than being estimated — a useful behavioral trait about data provenance and handling of missing values. It does not explicitly state read-only behavior, but the absence of side effects and the 'Return' wording imply it.

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?

Two concise sentences with no filler. The primary purpose is stated first, and the behavioral note about estimated values is supplementary. Every sentence earns its place.

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 tool, the description is adequate. It specifies the source (shared manifest) and the behavior for missing values. It does not detail the output structure, but given the lack of an output schema and the simplicity of the tool, this is a minor gap. The agent can call it without ambiguity.

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 has zero parameters, and the schema coverage is 100% (empty). Per the rubric, a tool with 0 parameters gets a baseline of 4. The description adds nothing about parameters because there are none, which is appropriate.

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 clearly states the action (Return) and the specific resource (BrunoSan access and pricing from the shared pricing manifest). It is distinct from sibling tools that focus on intelligence, domain inspection, or connection info, so the agent can identify its purpose unambiguously.

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 context (that pricing comes from a shared manifest) but does not explicitly state when this tool should be used versus alternatives, nor does it mention any exclusions. Usage is implied rather than expressed.

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