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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by specifying what is destroyed (the saved credentials for a single account) and confining scope to "one of the user's accounts." It does not say whether the deletion is reversible or whether re-authentication is required.

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, zero waste, with the destructive action front-loaded and the usage condition immediately after. Nothing could be cut without losing meaning.

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 one-parameter destructive tool with strong annotations and no output schema, the description covers action, target, and trigger condition adequately. Minor gap: it does not state that disconnecting requires reconnection via connect_integration, nor whether credential removal affects linked automations.

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% and the single parameter already carries an example ("email, telegram"). The description's "one of the user's accounts" loosely frames the parameter but adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource: "Remove the saved credentials for one of the user's accounts from Lodestone." An agent knows exactly what is being deleted and from where. It stops short of naming the inverse sibling (connect_integration), but the phrasing "disconnect or replace an account" ties it to that pair clearly enough.

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?

"Use only when the user asks to disconnect or replace an account" gives an explicit trigger condition and a restrictive "only" that discourages incidental use. It does not name the alternative tool (connect_integration) for the opposite operation, so routing is implied rather than spelled out.

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