aura_bulk_fetch

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

With no annotations, the description carries the full burden, and it does disclose two meaningful behavioral traits the schema cannot convey: the 2-8 item batch bound and the partial-failure model ('Per-item errors never fail the batch'). It still omits safety profile and whether ids are resolved per-item or atomically.

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?

Three short sentences with the core purpose front-loaded, then the alias note, then the failure semantics. No filler and nothing redundant.

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?

For a 2-param, no-annotation, no-output-schema tool, the description covers batching and error behavior but leaves the id format and the shape of a successful result unaddressed. It is adequate but has a clear gap in the one place an agent is most likely to guess wrong.

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%, so the description must compensate: it usefully constrains the `ids` array to 2-8 entries and echoes the `kind` enum values. However, it never explains what form an id takes (slug, uuid, name), which is the single most important thing for invoking this tool correctly.

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 concrete verb and resource (bulk-fetch 2-8 details) and scopes it to components, design_systems, or assets. Critically, it explicitly identifies itself as the alias of sibling tool aura_bundle, so an agent can tell the two apart without opening either schema.

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?

Gives a clear usage context (batch retrieval of 2-8 details in one call) and clarifies the relationship to aura_bundle as an equivalent alias, which is real routing information among 30+ siblings. It stops short of stating when to prefer a batch call over the individual get_* tools.

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