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

Annotations already mark the tool as readOnly and idempotent. The description adds value beyond those by disclosing that re-running refreshes the cached capability scan and clarifying how force_refresh relates to that cache. This is useful behavioral context without contradicting the annotations.

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 dense sentences front-load the core purpose, then add the cache-refresh behavior and the alias nuance. There is no filler, and each clause contributes to correct invocation.

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?

With a rich output schema, strong annotations, and fully documented optional parameters, the description covers the essential invocation context: what the tool returns, when cache is refreshed, and how to handle non-default aliases. Nothing critical is missing for an agent to select and call it correctly.

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%, with both 'alias' and 'forceRefresh' already well described in the input schema. The description only lightly reinforces the alias behavior and cache refresh; it does not add substantial new parameter meaning beyond what the schema already provides.

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 verb ('Return') and resource ('full orientation envelope for a registered BrAPI connection') and unpacks what that envelope contains: server identity, capabilities, content counts, and notes. This distinguishes it from data-querying siblings like brapi_raw_get or brapi_find_studies, since it is specifically about connection metadata.

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 implies the tool is for inspecting an existing BrAPI connection and notes when to pass an alias ('pass an alias to read a non-default connection'). It does not explicitly name alternatives or state when not to use it, but the context of a registered connection and the sibling set make the intended use reasonably clear.

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