family_mcus

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

No annotations are provided, so the description carries the full burden. It does disclose what comes back at a high level ('memory/package metadata'), but it says nothing about ordering, pagination/truncation behavior implied by the limit parameter, or what happens when a family has more than the limit.

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?

A single compact sentence with the resource and scope front-loaded and an example inline. No filler and nothing to remove.

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 no output schema, the description should at least sketch the return shape; 'memory/package metadata' gives a hint but leaves the actual fields unspecified. For a simple two-parameter read tool this is adequate but not complete, and pagination behavior remains unaddressed.

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%, so both parameters are already documented in the schema. The description reinforces the family parameter with an example (STM32H7), but adds nothing about the limit parameter or its relationship to truncation, so it stays at baseline.

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 and resource ('List the MCUs of one family') and includes a concrete example (STM32H7), so an agent can tell this is enumeration within a single family. It does not explicitly contrast with nearby siblings such as mcu_search, mcu_info, or family_list, so the differentiation is only implied.

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 phrasing 'of one family' implies a prerequisite (you must already know the family name) and hints that this is a scoped enumeration rather than a global search. However, there is no explicit guidance on when to use this instead of mcu_search or mcu_info, and no stated exclusions.

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