print_latex_expression

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

With no annotations, the description carries the full burden; 'Prints' implies a non-mutating read, and it usefully discloses that variable assumptions are included in the output. It does not say how an unknown or stale expr_key is handled, nor confirm that no state changes occur.

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?

One sentence, front-loaded with the action and format, with the one non-obvious detail (assumptions are printed too) placed immediately after. Nothing wasted.

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?

An output schema exists, so return structure needn't be described. However, for a one-parameter lookup the description omits how to source expr_key and what failure looks like, leaving a noticeable gap.

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 coverage is 0% — 'Expr Key' is an undocumented string. The description contributes the meaning that the key refers to a previously stored expression, which is genuinely useful, but it doesn't describe the key's format or where an agent obtains one.

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?

States a specific verb and resource ('Prints a stored expression in LaTeX format') plus the added content ('variable assumptions'), which tells an agent exactly what comes back. It doesn't mention the sibling print_latex_tensor, but the expression/tensor distinction is evident from the names.

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?

'Stored expression' implies a prerequisite — an expression must already exist via introduce_expression — but the description never states that or names alternatives. Usage is inferable rather than explicit.

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