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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that: it discloses what the tool returns (click-by-click steps, links, screenshots, values to collect) and the intended interactive pattern, which is real behavioral context.

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?

Three sentences, front-loaded with the core purpose and organized as purpose → usage → parameter note. Each sentence earns its place, though the final provider clause is slightly repetitive of the schema description.

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?

With no output schema, the description compensates by describing the return content and the interactive follow-up. Combined with 100% schema coverage and clear annotations, an agent has enough to call it correctly; only the link to connect_integration as the subsequent step is left implicit.

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 coverage is 100%, so the baseline is 3, but the description adds conditional semantics not in the schema: provider is only relevant for email and should be passed 'once you know it,' with the accepted values restated to tie the parameter to a real choice point.

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 names a specific verb and resource: 'Get the step-by-step walkthrough for connecting one account to Lodestone.' It goes further to specify exactly what the walkthrough contains (where to click, exact links, screenshots, values to ask the user for), so an agent can distinguish this from siblings like integration_status (status lookup) and connect_integration (performs the connection).

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?

It prescribes the workflow clearly: read the guide, then walk the user through it one step at a time and collect values in-chat, and it references integration_status as the source of the integration id. It does not explicitly name connect_integration as the follow-up action or state a when-not condition, so it stops short of full alternative routing.

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