recommend_architecture_tool

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by specifying that the tool performs a comparison and returns a reasoned classification, alternatives, and risks. This is consistent with the annotations, and no contradiction exists.

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 single front-loaded sentence that states the action and the expected output without any filler. Every word contributes meaning, making it appropriately concise and well structured.

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?

The output schema exists and annotations provide the safety profile, so return values and side effects are largely covered. However, the description still leaves clear gaps around when to use the tool and what the 'project' parameter must contain, making it minimally viable rather than fully self-contained.

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 description coverage is 0%, and the description does not explain the required 'project' parameter at all. The schema only indicates a free-form object with additionalProperties true, so the agent receives no guidance on what fields or structure the project object should contain.

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 uses a specific verb and resource: 'Compare integration patterns' and states the output as 'a reasoned classification, alternatives and risks.' It is clearly distinguishable from sibling tools like compare_bom_options_tool because it targets integration patterns rather than BOM options, though it does not explicitly name any sibling.

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 provides no guidance on when to use this tool versus alternatives such as assess_existing_infrastructure_tool or analyze_inference_project_tool. It also gives no context about the workflow position or prerequisites, leaving the agent to infer usage solely from the tool name.

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