list_connections

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

Discloses behavioral traits: 'active connection is shown first' and 'API secrets are masked.' No annotations are provided, so the description adds necessary transparency. Minor gap: does not mention whether it returns all connections or just the active one, but the context is sufficient.

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?

Three sentences cover purpose, behavior, and usage guidance without waste. Information is front-loaded and each sentence adds value.

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?

Given no parameters, no annotations, and an output schema (though not shown), the description fully equips the agent to understand the tool's purpose and behavior. The tool is simple and the description covers all necessary aspects.

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 with 100% coverage. The description adds context beyond the schema by explaining the output ordering and masking behavior, making it clear what the tool does without needing 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 clearly states the verb 'list' and the resource 'saved Frappe LMS connections' from the local database. It distinguishes the tool from siblings by specifying it lists connections rather than courses or other entities.

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 states 'Use this to see which Frappe instances are configured and which is active.' This guides the agent on when to invoke this tool, differentiating it from other tools like switch_connection.

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