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

No annotations are supplied, so the description carries the full burden. It discloses the key behavioral fact that an empty query returns the full list and that tier filtering is available, but says nothing about match semantics (substring vs. fuzzy, case sensitivity), result ordering, or default/maximum page size — meaningful gaps for a search tool where an agent must predict result volume.

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 no filler, front-loaded with the core action and ending with sibling routing. Every clause carries distinct information; nothing restates the tool name or the enum already in the schema in a wasteful way.

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?

There is no output schema, so the description should at least indicate what a result contains (e.g., item name, tier, identifier) — it does not. Combined with the undocumented limit/offset parameters and absent match/ordering semantics, an agent must guess how to page through and interpret results, though the core selection logic is adequately covered.

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 for all four parameters. It clarifies `query` (empty means list-all, matched against name and description) and gives meaning to `tier`, but `limit` and `offset` are entirely undocumented in both schema and description, leaving pagination semantics undefined for a tool that clearly paginates.

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 ('Search Frontic UI items') plus the searchable fields ('by name and description'), and explicitly contrasts itself with get_item_docs and get_item_examples. An agent can distinguish this from all three listed siblings without opening any 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 clear usage conditions: an empty query lists everything, and `tier` narrows results. It also routes the agent to alternatives, naming get_item_docs for reading a single item and get_item_examples for examples alone. It stops short of any when-not-to-use or prerequisite statement, so it is strong but not exhaustive.

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