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

No annotations are provided, so the description carries the disclosure burden. It meaningfully explains that export returns the key pair and that this key authorizes post-session Bureau actions, which is important behavioral and security context.

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?

The description is a long, convoluted run-on with heavy jargon. The important export behavior is buried mid-paragraph rather than front-loaded, making the definition harder to parse than necessary.

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?

There is no output schema, so the description must explain return values. It sketches the returned fields at a high level and explains the export mode, but it omits formats and relies on obscure domain terminology, leaving gaps for an agent unfamiliar with the context.

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 coverage is 100%, so the parameter is already documented. The description adds substantive meaning beyond the schema by explaining that the exported key can be saved as the SDK key file or reused with use_key, and that the kept key governs later Bureau calls.

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 identifies the returned session identity fields (address, name, table-open status), but it never states the purpose with a clear verb like 'returns'. Domain jargon such as 'city', 'wire', and 'table' makes the tool's exact purpose less immediate than it could be.

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?

It gives specific guidance for export=true: save the key pair as the SDK's key file or bring it back with use_key. However, it does not explain when to call whoami versus siblings or when to leave export false.

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