get_setup_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. 'Get detailed setup instructions' clearly signals a read-only, side-effect-free retrieval operation. It could add detail about whether instructions are static or fetched externally, but for a zero-parameter guide lookup the behavior is adequately disclosed.

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 12-word sentence that front-loads the verb and resource, then adds illustrative provider names. Every word contributes to conveying meaning; there is no filler or 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 tool with an output schema present, the description fully covers the purpose and scope. The output schema handles return-value details, so nothing an agent needs to invoke the tool correctly is missing.

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?

There are zero parameters, so the description carries no parameter-documentation burden. Per the baseline for an empty parameter list, 4 is appropriate; the description correctly implies that no provider selection is needed.

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 uses a specific verb-resource pair ('Get detailed setup instructions for email providers') with concrete examples (Microsoft OAuth2, Gmail, Zoho). It is the only sibling tool whose purpose is obtaining setup guidance, so an agent can immediately distinguish it from the message-operation and account-verification tools.

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 makes the use context clear: use this tool when you need setup instructions for email providers. It does not explicitly state when not to use it or name alternatives, but there are no competing siblings for this purpose, so the context is unambiguous.

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