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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered by structured data. The description adds the returned field set and browsing semantics, but says nothing about pagination, result size, or ordering for a 'list all' operation. Adding some value over annotations, but not rich behavioral 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?

Two sentences, no waste. The resource description and returned fields come first, and the routing guidance to `search` follows immediately.

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 an output schema present, annotations covering the safety/idempotency profile, and a fully documented single optional parameter, the description only needs to state what it lists and when to prefer it, which it does.

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?

There is only one optional parameter (locale) and schema description coverage is 100%, including the enum values and the 'Default: en' note. The description adds no parameter-level information, which is acceptable given the schema fully documents it.

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?

States a specific verb (List) and resource (reference architectures), and defines the term inline as 'end-to-end enterprise agentic blueprints' so the agent knows exactly what domain object is returned. It also enumerates the returned fields, making the scope unambiguous against retrieval siblings like get_architecture.

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?

Explicit routing instruction: browse with this tool, or use `search` when starting from a use case rather than a name. This is a clear when-to-use and when-to-use-something-else statement naming the alternative sibling.

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