get_institutions

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

With no annotations, the description serves as the sole behavioral disclosure. It conveys a read-only operation and the scope ('all institutions linked to monarch money'), but offers no details about output format, pagination, ordering, or other runtime behaviors. Sufficient for a simple zero-param read, but nothing beyond the basic operation.

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 one short sentence with no wasted words. Every piece of it ('all', 'financial institutions', 'linked to Monarch Money') contributes directly to understanding the tool's scope and behavior.

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 tool, the description covers the essential purpose and scope. The main gap is the lack of an output schema or return-format note, so an agent must infer the response shape; the low complexity makes this acceptable.

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 tool has zero parameters, so the input schema is trivially complete. There are no param semantics to explain, and the description need not add anything; the baseline for zero-param tools is 4.

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 ('Get') and resource ('all financial institutions linked to Monarch Money'), clearly distinguishing it from sibling tools that handle transactions, accounts, cashflow, and categories. An agent can immediately identify what this tool does without opening the schema.

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 provides no guidance on when to use this tool versus alternatives such as get_account_details or get_transactions. It is clear what the tool retrieves, but not when it is the appropriate choise over it siblings.

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