fleet_search

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

No annotations provided, so the description bears full responsibility. It mentions semantic search and returns ranked results with conservation metadata, but omits critical behavioral traits such as read-only status, whether it modifies data, authentication needs, or rate limits. This leaves the agent underinformed.

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, directly stating purpose and what the tool returns. No fluff, every word earns its place. Structure is optimal for quick comprehension.

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 description is adequate for a simple search tool with two parameters and no output schema. It clarifies the search scope and output type, but could be more complete by mentioning output format or error conditions, especially given no output schema.

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% with both parameters ('query' and 'topK') having clear descriptions in the schema. The tool description adds no additional meaning beyond what the schema already provides, meeting the baseline for complete schema coverage.

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 the tool performs semantic search across multiple specific resources (SHOAL oracle, fleet vector index) for patterns, crates, solutions, and knowledge, and returns ranked results with metadata. This distinguishes it from sibling tools like 'crate_info' or 'conservation_check'.

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?

The description implies the tool is for general search across the fleet, but does not explicitly state when to use it versus siblings or provide exclusions. Usage guidance is only implied, not direct.

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