Explain how to connect an existing FinalPeace account so the member tools (vault contents, personal checklist progress, next steps) become available. Use this only if someone says they already have a FinalPeace account and wants their own data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already signals a non-mutating operation, and the description reinforces this by saying the tool 'Explain[s] how to connect' rather than actually performing the connection. It adds context about what becomes available after connecting, which is useful beyond the annotation.
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 sentences long, front-loaded with the core action, and contains no filler or redundant information. Every clause contributes either to what the tool does or when it should be used.
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 explanation tool, the description adequately covers what it does and when to invoke it. It could add slightly more detail about the content of the explanation, but the current description is sufficient for an agent to select and invoke the tool correctly.
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 input schema has zero parameters, and schema description coverage is 100%, so there are no parameter semantics to clarify. With no parameters, the baseline is 4, and the description appropriately does not attempt to document nonexistent 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 uses a specific verb-resource pairing: 'Explain how to connect an existing FinalPeace account' and clearly states the intended outcome ('member tools ... become available'). It distinguishes itself from sibling tools, which are about assessment and document requirements rather than account 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?
The description gives an explicit condition for use: 'Use this only if someone says they already have a FinalPeace account and wants their own data.' This provides clear when-to-use guidance, though it does not name excluded alternatives or mention any alternate tools for users without an existing account.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct scenario: assessing planning gaps, connecting an account, looking up state requirements, and getting after-loss steps. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern (assess, connect, find, get + specific object). The naming is clean and predictable.
Four tools is a reasonable scope for this niche informational server—not excessive, but slightly minimal given the broader estate-planning domain.
Core informational needs are covered (assessment, legal requirements, after-death checklist), but connecting an account promises member tools that are not present in this set, creating a dead end for accessing actual user data.
