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

With no annotations provided, the description carries the burden. It discloses the heuristic nature and the need to verify against datasheets, which is useful. However, it does not mention fallback behavior (e.g., category listing when no match), price coverage limitations, or read-only characteristics; these are partly covered in the schema but not in the description itself.

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 three sentences long, front-loaded with the main purpose, followed by the return behavior and a necessary caveat. Every sentence adds useful information with no redundancy or fluff.

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?

No output schema exists, so the description should clarify return details. It mentions per-category candidates and reasons but omits count semantics, scene_matched flag, and price_fit behavior. However, the schema's parameter descriptions compensate for budget and application behavior, making the tool invocable despite the gaps.

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 100%, so the schema fully documents all three parameters. The description only repeats the budget parameter's existence without adding new meaning, and it does not explain count or application semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 tool recommends component combinations by application scenario and returns per-category candidates with reasons. It also characterizes the recommendation as heuristic and non-authoritative, which helps differentiate it from the sibling search_components tool, though it does not explicitly name that alternative.

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 clearly implies use for application-based recommendations and adds a caveat that it is not engineering advice. The application parameter's schema description explicitly directs users to search_components when no matches occur, providing an alternative path, but the main description lacks explicit when-not-to-use guidance.

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