Search CordFind Generator Guides

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds that results include direct CordFind source URLs, which is useful, but it does not detail response shape, pagination, or error behavior. This modest addition is reasonable given the annotations.

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 concise sentences with no filler. The core search action and subject matter are front-loaded, and the result detail in the second sentence is directly useful to an agent. Every sentence earns its place.

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?

For a simple read-only search tool with fully documented parameters and safety annotations, the description covers the essential behavioral context. It includes result behavior (direct source URLs), though it does not specify the full result structure since no output schema is provided. Slightly more detail on return format would make it fully complete.

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 query and limit documented in the input schema. The description's topic list helps inform what to put in the query but does not add meaning beyond the schema. This aligns with the baseline for fully covered parameters.

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 a specific action ('Search CordFind') and a specific resource ('generator cords, plugs, sizing, transfer equipment, maintenance, and safety guidance'). It also notes that results include direct source URLs, which further clarifies the tool's purpose and distinguishes it from the more specialized sibling tools.

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 when to use the tool by listing the topics it covers, but it does not explicitly mention when to avoid it or prefer a sibling like calculate_generator_cord_size or get_connector_compatibility. The usage context is present but the alternatives are not clearly routed.

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