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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description earns credit for disclosing that specs are demo/educational and flagged demoData, a data-quality caveat not present in structured fields. It says nothing about result ordering, pagination beyond the schema's default 25, or what an empty result set looks like.

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 compact fragments, with the corpus scope front-loaded before the filter list. The trailing field enumeration is slightly redundant with the schema but is short and scannable.

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 8 optional parameters and no output schema, the description should say roughly what comes back (a list of model records with demoData flags) and what happens with no filters. It covers scope and facets but leaves the return shape and default-call behavior to inference.

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 88%, so the schema already documents q, type, brand, length bounds, propulsion and trailerable. The description merely restates the same field names and adds no format or matching-semantics detail (e.g. whether q matches brand+model, whether type is an exact id). Baseline 3 applies.

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 Boat Day boat model graph') and scopes the corpus to US recreational models, which clearly separates it from the singular 'get_boat_model' sibling by implication. It stops short of explicitly naming the sibling or stating that a single-model lookup belongs elsewhere.

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 the facet list ('Filter by q, type, brand, length, propulsion, trailerable'), which tells an agent this is the multi-result browse tool. However there is no explicit when-to-use statement, no mention of when to prefer get_boat_model, and no note that an unfiltered call returns the default page of results.

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