Get operator workflow guide

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

Annotations include readOnlyHint=true, openWorldHint=false, destructiveHint=false. Description adds context: it returns a guide with specific content, does not fail on unknown operators, and is read-only. No contradictions.

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?

Two sentences, 39 words, front-loaded with 'Read-only'. Efficient and clear. No wasted words.

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?

Tool has 3 parameters with full schema coverage, output schema exists, and description covers main purpose and edge case. No missing behavioral info.

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 covers all 3 parameters with 100% description coverage. Description adds high-level context about 'inputs, outputs, examples, and next-operator suggestions' but does not expound on individual parameter meanings beyond schema.

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?

Description clearly states verb 'return', resource 'operator workflow guide', and content (inputs, outputs, examples, next-operator suggestions). Separates from siblings like search_operators by specifying it returns a guide, not just search results.

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?

Provides clear context: read-only, returns guide for known operators, and for unknown operators returns candidate guide ids instead of failing. Does not explicitly list alternatives or when not to use, but implied differentiation from similar tools.

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