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

Beyond the annotations, the description adds meaningful behavioral context: concurrent named aliases, server-side credential resolution, the return of an orientation envelope, and the distinction between built-in known servers and operator-configured aliases. It aligns with openWorldHint and idempotentHint, and while it doesn't cover lifecycle details like disconnection, the extra context is valuable.

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 front-loaded with the core purpose and prerequisite role, then proceeds through alias behavior, credential handling, and known servers with no filler. The longer enumeration of built-in servers and configured aliases is directly actionable, not padding.

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?

Given that the schema is rich, the output schema is present, and annotations cover safety/idempotence, the description is complete enough for an agent to call this tool correctly. It covers connection intent, authentication modes, alias shortcuts, built-in endpoints, and how to reach arbitrary servers via baseUrl.

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 schema already describes all three parameters thoroughly (100% coverage), but the description significantly extends that with deployment-specific alias names, built-in server identifiers, and guidance on when baseUrl and auth can be omitted. This is exactly the kind of practical parameter semantics that an agent cannot infer from the schema alone.

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 opens with a specific verb and resource combination: 'Open a connection to a BrAPI v2 server, authenticate, and return the full orientation envelope.' It also clearly positions the tool as the 'Required handshake before other BrAPI tools,' which differentiates it from the many data-access sibling tools in a single sentence.

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 when-to-use guidance ('Required handshake before other BrAPI tools') and practical context for omitting auth or baseUrl when using known servers or configured aliases. It stops short of explicitly naming alternatives or when-not scenarios, though for a connection-establishment tool the guidance is largely sufficient.

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