evaluate_expression

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which signal safe, non-destructive, idempotent behavior. The description echoes this by indicating evaluation without side effects. No contradictions, and the description adds context about what the tool evaluates (SpEL against execution context), but behavioral disclosure is mostly covered by annotations.

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?

A single, concise sentence that front-loads the key action and resource. No unnecessary words or information.

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 simplicity of the tool (two required params, no output schema, clear annotations), the description is sufficient to understand its purpose. However, it lacks details on the format of the expression or return value, which could be inferred but not explicitly stated. For a straightforward evaluation tool, this is nearly complete.

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 100% with clear parameter descriptions for execution_id and expression. The description adds minimal additional meaning beyond the schema, stating only that the evaluation is against a pipeline execution context. Baseline 3 is appropriate since schema covers all parameters adequately.

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 verb 'Evaluate' and the resource 'SpEL expression against a pipeline execution context', which is distinct from siblings like get_execution (which likely returns execution state) or list_executions. It precisely indicates what the tool does without ambiguity.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among siblings. The context of evaluating expressions is implied but no comparative advantage or restrictions are stated.

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