Get audit guide

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the return format (markdown), the content of the returned guide, and the lack of session/browser prerequisites. This gives the agent a solid mental model of a side-effect-free information retrieval operation.

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 front-loaded with the core behavior, uses a compact colon-list to convey rich content detail, and includes only two short supporting sentences about when to call and prerequisites. Every sentence adds distinct value without redundancy.

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 parameterless, read-only guide-retrieval tool, this description is complete: it states what is returned, what topics are covered, when to call it, and what is not needed. The sibling list further confirms the tool's role relative to audit execution and browser-control tools.

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 tool has zero parameters and the schema is empty, so there is nothing for the description to clarify beyond confirming no inputs are needed. The description adds context by noting that no session or browser is required, which is more valuable than restating parameter names.

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 verb and resource: it 'returns the step-by-step accessibility audit workflow for agents as markdown.' It clearly distinguishes itself from execution tools like run_a11y_audit by framing itself as the preparatory guide rather than the audit itself.

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 gives clear when-to-use guidance: 'Call this before starting an audit.' It also specifies that 'Needs no session or browser,' which tells the agent no setup is required. It does not explicitly name alternatives or when not to use it, but the context is strong.

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