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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds useful context about scope and entrypoint sequencing, but it does not describe what the tool actually returns or how it behaves at runtime beyond being a starting point.

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 with no filler. The scope is front-loaded and the final directive 'Call this first' is crisp. The lengthy verb list is dense but purposeful, covering the full recipe lifecycle in one compressed clause.

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 zero-parameter tool with annotations and an output schema, the description provides the essential selection context: it is the first-call discovery tool covering the full StewAI recipe lifecycle. Nothing critical is missing for an agent to decide when and why to invoke it.

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, so there is nothing to document and the baseline 4 applies. The description imposes no parameter expectations and the schema already confirms the tool takes no input.

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 makes clear this is the discovery/entrypoint tool for StewAI recipes and broadly states what an agent can learn about: authenticate, discover, preview, run, author, qualify, commit, inspect, and recover. It is distinguishable from the sibling tools, which are specific operational recipe actions, but the framing as 'learn how' is slightly indirect about what the tool actually returns.

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?

'Call this first' is an explicit, actionable usage directive that tells the agent when to invoke this tool before any sibling operations. It does not explicitly name alternatives or exclusions, but the sequencing guidance is clear given the list of operational sibling tools.

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