workflow_scan_repository_context

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds nothing behavioral beyond that: no indication of what gets scanned, how expensive/wide the scan is, or what a 'summary' contains. With annotations carrying the safety signal, the description fails to add the additional context that would earn a higher score.

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 compact sentence with no wasted words and the core action front-loaded. It is efficient, though brevity here comes partly from under-specification rather than precision.

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 read-only, single-parameter tool with no output schema, the description is roughly the minimum viable: safety is covered by annotations and no return values need explaining. It still leaves the required journeyId undocumented and the scan scope and sibling boundaries unclear, so it is adequate but noticeably thin.

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 single required parameter journeyId has 0% schema description coverage and is never mentioned in the description, so its meaning (which journey's repository context is scanned, and why it is required) is left entirely unexplained. The description does not compensate for 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?

States a verb ("Scan and summarize") and a resource ("repository context"), so the action is identifiable. However, "repository context" is vague and the description never differentiates this tool from close siblings such as workflow_onboard_repository or workflow_get_repository_graph, which sound like they could do the same thing.

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 phrase "for onboarding or graph building" implies when the tool is relevant, giving implied usage context. It names no alternative tools and gives no exclusion criteria, so an agent cannot tell from the description alone when to prefer this over the sibling onboarding/graph tools.

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