Retrieve passport dimensions, FairHelm coefficients, and canonical links for a yacht brand and model from a local snapshot to support specification lookups without decoding listings.
Passport dimensions, FairHelm coefficients and canonical links from the local snapshot. Does not decode listings.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | Yes | Brand slug, e.g. bavaria | |
| model | Yes | Model slug, e.g. bavaria-41 |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It adds useful context by saying the data comes from a local snapshot and that it does not decode listings, but it omits read-only implications, error behavior, and return shape details.
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 sentences and front-loads the returned content before adding the exclusion. It is efficient, though the jargon-heavy terms reduce immediate clarity.
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?
The tool is simple with two required parameters and no output schema. The description enumerates the data categories and snapshot source, but it does not explain return structure, failure behavior, or how this differs from compute_yacht_coefficients.
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%, so the schema already documents both parameters as brand and model slugs with examples. The description does not add parameter meaning beyond what the schema provides.
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 clearly states that the tool returns passport dimensions, FairHelm coefficients, and canonical links from a local snapshot, and scopes it away from decoding listings. However, it does not distinguish this tool from sibling tools such as compute_yacht_coefficients or list_yacht_models.
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?
There is no explicit guidance on when to use this tool versus the sibling tools. The only usage-adjacent statement is that it does not decode listings, which is a scope exclusion but not alternative routing or prerequisite guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.