search_geo_series

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

With no annotations provided, the description must fully convey behavioral traits, but it only states 'Search GEO Series'. It does not disclose expected behavior such as result format, pagination (though retmax exists), rate limits, or whether it requires network access. The agent is left unaware of key operational 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 extremely concise: a single phrase. It is front-loaded with the key action and resource. While it lacks structural elements like full sentences, it is not verbose and gets the core idea across efficiently.

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 the tool has only 2 parameters, no annotations, and no output schema, the description is insufficiently complete. It does not explain what results look like, whether they include metadata or just identifiers, or how to interpret the output. The presence of many sibling tools further demands differentiation that is missing.

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% (both term and retmax have descriptions), so the baseline is 3. The description adds no extra meaning beyond the schema, such as example term formats or the impact of retmax on result truncation.

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 states 'Search GEO Series (GSE) - complete experiments', making clear the tool searches for GEO Series entities. The phrase 'complete experiments' provides additional context, but it does not explicitly differentiate from sibling tools like search_geo_datasets or search_geo_samples, which search related but distinct entity types.

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?

No guidance on when to use this tool versus the many sibling search tools (e.g., search_geo, search_geo_datasets). There is no mention of typical use cases or when to prefer one over another, leaving the agent to infer based solely on entity names.

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