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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the trailing "Read-only" only confirms them. The description earns credit for disclosing semantics annotations cannot: the full verdict enum, that totals include missing baseline screenshots, that blocking[] carries per-item detail, and notably that verdict=failed conflates rejections with dropped baseline screenshots.

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?

Front-loaded with the three operations, then the high-value gate return contract, with no filler sentences. Minor waste is repeating "Read-only" already asserted by readOnlyHint=true annotations.

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 compensates for the gate path by enumerating verdicts and blocking fields. However, list and get return shapes and pagination behavior go unmentioned, leaving an agent guessing about the other two action paths of this 8-parameter tool.

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 100%, including action enum meanings, build_id/build_name dual usage, and the client-side substring caveat, so the schema already carries parameter semantics. The description only re-expresses action=gate usage and adds no syntax or constraint beyond the schema — baseline 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?

The first sentence names the resource (SmartUI builds) and all three distinct verbs/operations (list, get, gate verdict), so an agent can map action values to intent without opening the schema. The resource itself separates it from smartui_project_query and smartui_comparison_query siblings.

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?

"Use action=gate in pipelines" gives an explicit context that selects one of the three actions, which is real routing guidance. It stops short of saying when NOT to use this tool or naming SmartUI siblings (e.g. baseline/comparison tools) as alternatives for related questions.

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