reference-workflow-overview

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

No annotations are provided, so the description carries the full burden. It states the tool returns a 'guide' (read operation), but does not disclose any potential side effects, authentication requirements, or format of the output. The description is adequate but lacks depth on behavioral traits beyond the basic read nature.

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, well-formed sentence that conveys the essential information without any superfluous text. It is front-loaded with the action ('Get') and resource, making it easy to parse quickly.

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 (no parameters, no output schema), the description adequately explains what the tool returns: a high-level workflow guide. It does not specify the format or length, but for a reference-like tool, this level of detail is sufficient. The context signals confirm it is a simple retrieval tool.

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 input schema has zero parameters, and schema description coverage is 100% (vacuously). With no parameters, the description does not need to add parameter semantics. The baseline for 0 parameters is 4, and the description appropriately says nothing about parameters.

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 tool retrieves a 'high-level workflow guide explaining the test creation process and prompt relationships'. The verb 'Get' and resource 'high-level workflow guide' are specific, distinguishing it from sibling reference tools that focus on detailed topics like selector strategies or fixture patterns.

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 implies it should be used for an initial overview of the test creation process and prompt relationships. While it does not explicitly state when not to use or name alternatives, the sibling names (e.g., 'reference-core-principles', 'reference-selector-strategies') provide clear context that this is the general guide vs. specific references.

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