Privacy Bridge Status

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by detailing exactly what is read (pause/deposit policy, blacklist status, limits, fee quote) and confirming keylessness, going beyond the annotations without contradiction.

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 sentences: the first efficiently lists the tool's capabilities, the second clarifies key properties (keyless, read-only). No superfluous words, front-loaded with the primary action.

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?

The description covers the tool's purpose and scope adequately given the rich annotations. It does not describe output format, but for a read-only query tool with no output schema, the description is sufficiently complete for an agent to understand what it retrieves.

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?

Despite low schema description coverage (25%), the description maps each parameter to its functional role: 'pair' for the bridge pair, 'amount' for the optional fee quote, 'wallet' for blacklist status, and 'direction' implied for the fee quote direction. This adds meaningful context that the schema lacks.

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 specifies the verb 'read and verify' and the resource 'Privacy Portal bridge pair', listing concrete aspects like pause/deposit policy, wallet blacklist, limits, and fee quote. This clearly distinguishes it from sibling tools that are prepare/write tools.

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 states it is 'keyless and read-only', implying use for status queries. However, it does not explicitly contrast with sibling tools or provide when-not-to-use guidance, though the read-only nature serves as a strong hint.

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