Analyze Workflow

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

The description does not disclose that analysis likely reads/writes session state (readOnlyHint is false), or what effect invoking it has. 'Analyze' suggests a read-only operation, but the annotations and session_id parameter indicate possible side effects, so the description under-discloses 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 efficient sentence with no redundant wording and the core action front-loaded. It errs on under-specification rather than bloat, but the structure itself is clear.

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?

With no output schema, the description should explain what an analysis produces or returns; it does not. It also omits the session read/write behavior implied by readOnlyHint=false, leaving the agent without enough context to invoke the tool or interpret results safely.

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 description clarifies that the 'artifact' property is an AgenticLens-compatible workflow object, adding meaning beyond the bare schema entry. However, it says nothing about session_id semantics and the schema already documents session_id, so the added value is marginal.

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 names a concrete action and target: 'Analyze an AgenticLens-compatible workflow artifact.' This is clearer than a tautology and identifies the resource type, but 'analyze' is generic and does not distinguish it from siblings like spec.validate_artifact or lens.report_summary.

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?

There is no statement about when to choose this tool over alternatives such as spec.validate_artifact or lens.report_summary. The only implied trigger is having a workflow artifact to analyze, which is too weak given the overlapping sibling tool names.

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