UICapsule

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context by disclosing what the read returns — install command, npm dependencies, and the full source of every bundled file — which signals a potentially large payload and helps an agent anticipate the response shape.

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 well-formed sentence that front-loads the identifier (by slug) and follows with the return contents. No filler, no redundancy with the title.

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 correctly shouldered the burden of describing return values, and it does so concretely (install command, deps, full file sources). It stops short of covering edge behavior such as an unknown slug or whether the payload is truncated, leaving a small gap for a tool whose output is the main deliverable.

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?

There is a single parameter with 100% schema description coverage ('Slug from search_components'), so the schema does the heavy lifting. The description only restates that lookup is by slug and adds no format or sourcing detail beyond what the schema provides, which is the correct baseline of 3.

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 (Get) and resource (one component by slug), and even enumerates the payload contents: install command, npm dependencies, and full source of every file. The phrase 'one component by slug' implicitly contrasts with the bulk/query nature of search_components, so an agent can distinguish the two without opening a 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?

Usage is only implied: retrieving a single component by its slug naturally follows a search, and the schema field notes 'Slug from search_components'. However, the description itself names no alternative, no when-not condition, and no prerequisite for obtaining a valid slug.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: an empty query returns the full catalog and results are ordered newest first. It omits pagination/limit behavior and whether tag filtering is conjunctive, though the latter is covered in the schema.

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?

Two tight sentences, front-loaded with the primary capability and then the degenerate-input behavior. Every clause carries information; nothing is padding.

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 three-parameter, read-only search tool with no output schema, the description covers the matching semantics, the empty-input case, and result ordering. The remaining gap is limit/pagination behavior, which the schema's bounds partly imply but the description never states.

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 67%, with tag and query documented in the schema and limit explained only by its default/min/max bounds. The description adds the semantic that an empty query means 'list everything, newest first', which meaningfully clarifies the query parameter beyond the schema's example text.

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 gives a specific verb and resource: search the UICapsule catalog for components, with both functional ('what a component does') and visual ('looks like') matching. It does not name or contrast with its sibling get_component, so an agent gets no explicit routing signal beyond the verb difference.

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?

Usage is implied by 'search by what a component does or looks like' and the empty-query escape hatch is documented, but there is no statement of when to prefer this over get_component or when a search is unnecessary. The agent must infer that get_component is for retrieval by identifier.

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