rank_anchorages

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

No annotations provided; description only states it ranks by comfort against forecast. Lacks details on side effects, authentication, or assumptions (e.g., units, missing data). Insufficient disclosure for a tool with zero annotation coverage.

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 sentences, front-loaded with the primary purpose. Second sentence provides necessary parameter detail. Minimal waste, though could be slightly more concise.

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?

Provides essential information for a ranking tool with no output schema and no annotations. Explains forecast format but does not mention output structure (ranking order, score format) or error conditions. Adequate but has gaps.

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%; description adds meaning by explaining that 'names' are anchorage names and 'forecast' is a list of steps with specified fields (wind_from_deg, wind_kn, swell_from_deg, swell_m). Adds significant value beyond raw schema.

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?

Description states verb 'rank' and resource 'anchorages' with a clear method (against a forecast). Distinguishes from siblings: find_anchorages_near (nearby, not rank), get_anchorage (single), list_sources (list).

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?

Tells user to fetch forecast from weather-mcp and pass specific fields, implying a prerequisite. Does not explicitly state when to use versus alternatives or mention exclusions.

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