Search GW1 builds

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

With no annotations, the description itself must disclose behaviors. It does mention that author fields are omitted unless includeAuthors is true, which is a useful behavioral detail. However, it does not disclose other traits such as whether the operation is read-only, rate limits, or the format of results, leaving gaps.

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 concise, with two sentences that front-load the main purpose and add a key behavioral detail. No redundant or unnecessary words.

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?

Given that there is no output schema and 4 parameters, the description is insufficiently complete. It does not explain what 'search' entails (e.g., matching behavior, fields searched), the return format, or any limitations. Sibling tools are similar but the description does not help an agent understand when the tool is the right choice.

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?

The description clarifies the effect of the includeAuthors parameter (authored fields omitted unless true) and hints that source selects between two data sources. However, it does not explain limit, query, or the source enum beyond the provided values. With 0% schema coverage, more parameter detail would be beneficial.

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 action ('Search') and resource ('GW1 Builds public API and/or PvXwiki build pages'), with a specific behavioral note. However, it does not differentiate from sibling search tools like gw1_content_search, which could be used for similar queries.

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 usage for searching build-specific content from two sources, but it lacks explicit guidance on when to use this tool versus alternatives like gw1_subreddit_search or gw1_wiki_search. No when-not-to-use or alternative suggestions are provided.

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