resolve_function

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'optionally auto-execute' but does not explain what auto-execution entails (e.g., running code, side effects, kernel requirements). The description omits clarity on permissions, rate limits, or destructive potential.

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 a single sentence of 10 words, which is concise but too minimal. It front-loads the core purpose, but every word should earn its place; here, the description is under-specified for the tool's complexity.

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?

Despite having an output schema (not shown), the description fails to explain what the search returns, how auto-execution interacts with results, or the meaning of parameters like expression, max_candidates, and output_target. For a tool with 5 parameters and an output schema, much more context is needed.

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 has 0% schema description coverage, meaning no parameters are explained in the description. With 5 parameters, the description should compensate for the lack of schema documentation, but it does not. Even the key parameter 'auto_execute' is only hinted at without explaining its impact.

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 it searches for Wolfram Language functions with optional auto-execution, which is a specific verb+resource. However, it does not differentiate from sibling tools like suggest_similar_functions, so it's not a 5.

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 such as suggest_similar_functions or entity_lookup. It does not mention when auto-execution is appropriate or when to avoid it.

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