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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing safety and idempotency. The description goes beyond by detailing the reconnect_url behavior (reauthentication without disconnecting), the response structure for bulk (count, items), and the executionStatus field. There is no contradiction with annotations, and the description adds significant behavioral context.

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 moderately concise, providing essential information in a structured manner. It front-loads the primary purpose and then elaborates on usage patterns. While every sentence adds value, the description could be slightly more terse, especially by combining the lines about bulk support. Overall, it is well-organized and readable.

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 the lack of an output schema, the description adequately covers the return fields (status, executionStatus, connector metadata, reconnect_url) and differentiates between single and bulk responses. It addresses the main usage scenarios. However, it does not mention error conditions or edge cases (e.g., what if an invalid item is given). For a read-only status tool, this is acceptable but not exhaustive.

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?

Although the input schema has 0% coverage (no parameter descriptions), the description explains how to use 'item' and 'item_ids' effectively: omitting item returns all, passing item returns single, and item_ids enables bulk. However, it does not clarify the difference between 'item' and 'item_id' (both in schema), leaving some ambiguity. This prevents a perfect score because the description should explain all 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 tool returns the current status of a bank connection, listing specific fields (status, executionStatus, connector metadata, reconnect_url). It distinguishes between retrieving all connections versus a single one, and mentions bulk support with item_ids. Compared to sibling tools like openfinance_list_connections, which likely lists connections without status details, this tool's purpose is specific and well-defined.

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 clear context on when to use the tool: to get connection status. It explains different usage patterns (omit item for all, pass item for single, use item_ids for bulk). However, it does not explicitly state when not to use it or contrast with similar sibling tools like openfinance_list_connections or openfinance_provider_status. This omission prevents a higher score.

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