mathematica_differentiate

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

No annotations provided. The description does not disclose behavioral traits such as whether it handles symbolic or numeric differentiation, error conditions, or return format. With annotations absent, the description carries full burden but fails to address these.

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 one sentence, which is concise but severely under-specified. It front-loads the core function but lacks essential details, making it less useful than a more thorough but still concise description.

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 complexity of differentiation, the description is highly incomplete. It fails to mention syntax for expressions, supported functions, output structure (though output schema exists), or any constraints. Far from meeting the needs of an agent.

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%. The description adds no meaning to the three parameters (expression, variable, order). It does not explain that 'expression' is a symbolic math string, 'variable' is the differentiation variable, or that 'order' defaults to 1. Critical semantics are omitted.

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 'Compute derivative using D' clearly states the action and the Mathematica function used. It differentiates from siblings like mathematica_integrate, mathematica_limit, etc., but could be more specific about symbolic differentiation.

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 vs alternatives. For example, it doesn't mention that this is for symbolic differentiation or that mathematica_limit might be used for limits. The description only states what it does, not when.

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