search_doaj

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

No annotations; description does not disclose behaviors like rate limits, pagination, or read-only nature. Minimal behavioral info beyond basic search action.

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?

Short, well-structured using args/returns format. Every sentence is informative with no fluff.

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?

Output schema exists, so return details not needed. However, lacks context about DOAJ's scope (open access) and when to prefer this over sibling search tools. Minimal completeness among many similar tools.

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 coverage 0%, so description compensates by explaining 'query' (search string with example) and 'max_results' (max papers, default 10). Adds value beyond 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?

Clearly states 'Search academic papers from DOAJ', using specific verb 'Search' and resource 'academic papers from DOAJ'. Distinguishes from sibling download and read 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?

No explicit guidance on when to use this tool vs alternatives (e.g., search_arxiv, search_pubmed). User must infer from the DOAJ source name; no contextual hints about use cases.

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