Get a WunderUI block's source (Pro)

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Pro-key authentication requirement and describes what is returned (source plus shared helpers), but it omits error behavior, rate limits, and whether the operation has any side effects.

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 two tight sentences with no wasted language. The purpose and examples are front-loaded, and the licensing and discovery notes follow naturally.

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 simple three-parameter read tool with no annotations or output schema, the description covers purpose, authentication, parameter examples, and what is returned. It could clarify the return shape or format, but it is largely complete.

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 does so by explaining all three parameters semantically: category and block with examples, and screen as optional. It could specify allowed values more fully, but the registry URL helps.

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 states a specific verb and resource: retrieving the React source of a UI block, optionally for one screen, plus shared helpers. It gives concrete examples ('category app', 'block billing'), making the tool's output clear. However, it does not explicitly differentiate from siblings like get_component or list_components.

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?

It states a prerequisite (WunderUI Pro key in WUNDERUI_LICENSE_KEY) and points to a registry index URL for discovering blocks, which implies usage. But it gives no guidance on when to use this tool versus alternatives, and no exclusions or conditions are stated.

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