get_connection_status

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

Discloses what the tool shows (per-institution sync health, timestamps, login requirements, error states) beyond the readOnlyHint annotation. No contradictions; annotation reinforces the read-only nature.

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 with no wasted words. First sentence states purpose, second adds detail and usage guidance. Front-loaded with key information.

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?

Covers purpose, usage, and output details adequately for a parameterless read tool. Lacks explicit output structure format, but the description of what it shows is sufficient for correct invocation.

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?

No parameters exist, baseline score of 4. Description adds no parameter info because none are 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?

Clearly states it retrieves connection status for all linked financial institutions, specifying the resource (connection status) and the verb (get). Distinguishes from siblings like get_accounts by focusing on sync health, timestamps, login requirements, and error states.

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?

Explicitly says to use for checking last sync timestamps and identifying problematic connections, providing clear usage context. Does not exclude alternatives, but no sibling tool serves this specific purpose.

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