series

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention that the expansion point defaults to 0 (Maclaurin series), nor does it specify input constraints (e.g., expression must be symbolic) or output format. The description is insufficient for an agent to anticipate tool behavior.

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 short sentence, which achieves conciseness but at the cost of sacrificing necessary details. While it is front-loaded and efficient, it omits critical information that would fit in a slightly longer description without becoming 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 the complexity of series expansion and the existence of an output schema (not shown here), the description should at least hint at the return format (e.g., a symbolic expression). It fails to mention what the tool returns, its error behavior, or the scope of supported expressions (e.g., rational functions, elementary functions). This lack of completeness limits the agent's ability to use the tool effectively.

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 input schema has 0% description coverage, so the description must clarify each parameter's meaning. Although the phrase 'Taylor or Laurent series expansions' implies the role of expression, variable, point, and order, it provides no explicit mapping or additional constraints. For example, it doesn't detail that 'point' is the expansion center or that 'order' indicates the truncation order.

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 computes Taylor or Laurent series expansions, specifying the exact type of mathematical operation. It distinguishes from sibling tools like limit or symbolic_diff which handle different operations, leaving no ambiguity about the tool's core function.

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 limit or symbolic_integrate. There is no mention of prerequisites, typical use cases, or scenarios where a different tool would be more appropriate.

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