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

The annotations already establish that this is a non-destructive, read-only, closed-world operation. The description adds useful behavioral context beyond that: the returned opaque ID remains stable across reconnections, scope upgrades, and ledger renames, and it explicitly notes that no user email is returned. It does not cover authentication needs or response shape, but the output schema handles the latter.

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 short sentences, front-loaded with the core action, followed by stability guarantees and a notable return-value caveat. Every sentence adds distinct information without redundancy.

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 read-only identity lookup with an output schema and full annotations, the description is complete enough to call correctly. It explains what is identified, the stability property of the returned ID, and an important negative return fact (no email), leaving no material 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 takes zero parameters, so there is no parameter semantics burden. The schema description coverage is 100% and the baseline for no params is 4; the description does not need to explain parameters and appropriately does not try.

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 and resource: 'Identify this connection's bound ledger.' It clearly sets the tool apart from the travel, expense, loyalty, and journey siblings by framing it as a connection-level identity lookup, not a domain data operation.

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 implied by the purpose ('identify this connection's bound ledger'), but there is no explicit guidance such as when to call it versus relying on another tool or when it should not be used. The context is clear enough for an agent to infer, but no exclusions or alternatives are stated.

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