search_publications

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

No annotations are provided, so the description carries the full burden. It reveals the tool is a read operation (search) but does not disclose any other behaviors such as rate limits, authentication requirements, or result format.

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 consists of two concise sentences. The first front-loads the core purpose, and the second adds usage context. No fluff or redundancy.

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 tells when to use the tool but omits information about the return structure, pagination, or result format. Given the 6 parameters and no output schema, the description is adequate but not complete for an agent to fully understand usage without further inspection of the 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%, so the description's contribution is minimal. The description reinforces the purpose of query, author, and date parameters but adds little new meaning beyond the 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?

The description clearly states it searches Google Scholar for academic publications, papers, and research articles. The verb 'search' and resource 'Google Scholar' are specific, but it does not explicitly distinguish from the sibling 'advanced_search' tool.

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?

It says 'Use this to find papers on topics, by authors, or within date ranges,' which provides context for usage. However, it does not mention when not to use it or mention alternatives like 'advanced_search'.

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