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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description consistently describes an explanatory action rather than a mutation. It adds useful context that the tool unlocks member tools, but it does not disclose details such as credential requirements or the exact connecting workflow. No contradiction with annotations.

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 two tightly written sentences with the purpose front-loaded and the usage condition placed second. Every word earns its place; there is no repetition of the title or filler.

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, read-only explanation tool with annotations covering safety, the description supplies the trigger condition, scope, and result. The only conceivable addition would be guidance for users without an account, which is outside this tool's stated purpose.

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 input schema imposes no burden and there is nothing for the description to clarify. The baseline of 4 applies because the description does not need to compensate for undocumented parameters.

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 states a specific verb ('Explain how to connect'), a specific resource ('existing FinalPeace account'), and the intended outcome ('member tools ... become available'). It is clearly distinct from the sibling tools, which concern estate-planning gaps, document requirements, and after-loss steps.

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 gives an explicit trigger condition: 'Use this only if someone says they already have a FinalPeace account and wants their own data.' It does not name an alternative tool for the opposite case, but the 'only if' phrasing acts as a clear exclusion gate.

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