search_data_repository

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

No annotations are provided, so the description carries full burden. It only states 'Search the Wolfram Data Repository' without disclosing behavioral traits such as whether it is read-only, what the output format is, or if it requires an internet connection.

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 very concise (one sentence), which is good for front-loading, but it omits important contextual information. It could be longer to cover essential details without being verbose.

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 the tool has an output schema, the description does not need to explain return values. However, it lacks any contextual completeness such as examples, prerequisites, or relationship to sibling tools. The 0% schema coverage further compounds the lack of completeness.

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 0%, and the description does not elaborate on the parameters. While parameter names are somewhat self-explanatory ('query' as search term, 'max_results' as maximum results), the description adds no additional meaning or usage hints beyond the names.

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 tool's purpose: 'Search the Wolfram Data Repository.' It uses a specific verb ('Search') and a specific resource ('Wolfram Data Repository'), distinguishing it from sibling tools like 'search_function_repository' and 'wolfram_alpha'.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or relationships to sibling tools like 'search_function_repository' or 'load_dataset'.

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