expand_expression

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

With no annotations, the description bears the full burden of behavioral disclosure, but it only states the basic action. It fails to mention output format, side effects on the session workspace, error handling, or any limitations, leaving an agent without insight into the tool's 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 appropriately short with no wasted words, but it is under-specified for a tool with many similar siblings. Brevity here sacrifices crucial distinguishing information, making it less useful than a slightly longer description would be.

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?

Although an output schema exists and parameter schema coverage is full, the description lacks context for tool selection and usage. It does not explain what 'expand' means in this mathematical context, nor does it hint at when to prefer it over related operations.

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?

All parameters are already documented in the input schema (100% coverage), so the description adds no additional meaning. The schema describes 'expression' and 'session' sufficiently, and the description does not elaborate on how they interact.

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 action 'expand' on a 'mathematical expression', which is a specific verb and resource. However, it does not distinguish itself from sibling tools like 'series_expansion' or 'simplify_expression', so it lacks 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention what types of expressions are suitable, nor does it reference any sibling tools for comparison.

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