bitpull_site_accounts

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that by promising keys are excluded ('without their keys'), which matters for an agent handling credentials. It says nothing about what happens when no accounts are connected or how many results to expect.

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?

A single short clause with zero filler; the provider list and the key-exclusion caveat are both front-loaded. It reads as a fragment rather than a sentence, but nothing is wasted.

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?

With no output schema, the description is the only place to learn the return shape, and it never says what fields each account entry contains beyond the absence of keys. For a simple zero-arg read this is close to sufficient, but the result structure remains an inference.

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 takes zero parameters, which is the baseline-4 case per the rubric. There is no parameter meaning for the description to add or omit.

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 names a specific resource (hosting and database accounts connected on this computer) and enumerates the providers (Cloudflare, Vercel, Supabase, Neon, Upstash), so an agent knows exactly what it returns. It lacks explicit differentiation from nearby siblings such as bitpull_integrations or bitpull_connect_account_page, which keeps it from a 5.

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?

Usage is only implied: the phrase 'connected on this computer' scopes the query to local accounts, hinting at when to call it. There is no explicit when-to-use, no prerequisite, and no named alternative for related tasks like connecting or disconnecting an account.

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