workflow_analyze_journey

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

Annotations declare readOnlyHint=true, so safety profile is covered. The description adds 'deterministic' (results are reproducible) and 'evidence-gap analysis' (this is analysis output, not mutation), which is useful added context. But nothing about what it consumes from the manifest, whether it requires prior onboarding, or what it returns. With annotations carrying the safety burden, a 3 is appropriate.

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 compact sentence with no filler, front-loaded with the verb. It's efficient, but borderline under-specified rather than genuinely concise — it says a lot of words ('deterministic cross-repository Journey contract and evidence-gap analysis') without resolving what the agent actually needs.

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?

For a tool that takes a complex nested manifest and produces some analysis (no output schema), the description is far too thin. It doesn't cover the manifest requirement, processing semantics, what 'evidence-gap' means, or expected output. Given the complexity and density of siblings, this is inadequate.

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 description coverage is 0%, but there's only one top-level parameter ('manifest') and the schema documents its entire nested structure with required fields, types, and constraints. The description says nothing about the manifest or how it relates to cross-repository analysis. Baseline for a single richly-typed parameter is around 3; the description neither compensates for nor worsens the coverage gap.

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 states a specific action verb and resource: 'Run deterministic cross-repository Journey contract and evidence-gap analysis.' It says what it does at a high level, but it's jargon-heavy and doesn't tell the agent exactly what gets produced or how it differs from siblings like workflow_get_journey_graph or workflow_analyze_http_dependencies. It's distinct enough from the names alone, but the purpose remains somewhat opaque.

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?

No when-to-use guidance, no prerequisites or conditions, no mention of alternatives. With a dozen analysis/graph siblings (workflow_get_journey_graph, workflow_analyze_http_dependencies, workflow_scan_repository_context), the description does zero routing. Implied usage is running analysis, but nothing tells the agent when to pick this over the others.

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