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

With no annotations, the description carries the full behavioral burden. It discloses that omitted project/environment arguments inherit the authenticated workspace binding, that a registered adapter is not necessarily executable, and that credentialAvailability=not_checked means credentials/capacity are still quote-time concerns. These are non-obvious, decision-relevant behavioral facts.

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?

Five sentences, all high-signal: core output list, inheritance behavior, readiness caveat, credential caveat, and onboarding guidance. The description is front-loaded and contains no filler or repetition.

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?

An output schema exists, so return-value structure is already covered. The description supplies the remaining operational context: workspace binding behavior, routeCompatible requirement, credential semantics, and alias-inspection guidance. For a read-only discovery tool with optional parameters and no annotations, nothing important is missing.

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 has 0% description coverage and only type/default for each optional parameter. The description compensates by explaining the core semantic: omitted project/environment arguments inherit the authenticated workspace binding. It does not document accepted value formats or examples, but for two optional strings the inheritance rule adds meaningful meaning beyond the schema.

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: 'List the bound project's registered model adapters, semantic aliases, image-generation default, and static routing readiness.' This clearly distinguishes a discovery/listing tool from the many adapter-management, capability, and run siblings. Although the title says 'Choose model adapters', the description itself is unambiguous about listing rather than choosing.

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 concrete when-to-use guidance: check routingReadiness.routeCompatible before selecting an adapter for generation, and new agents should inspect project aliases before searching externally. It does not explicitly name sibling tools as alternatives or state when not to use this tool, so it stops short of a 5.

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