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

With no annotations, the description carries the full behavioral burden. It does disclose an important behavior: results include team-shared accounts, not just personal accounts. However, it does not mention pagination, response format, authentication requirements beyond the phrase 'authenticated user,' or any rate-limit considerations, so some behavioral transparency is missing.

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 a single concise sentence that front-loads the action and resource, then adds the important scoping detail about shared accounts. Every word earns its place with no redundancy or filler.

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 simple, zero-parameter list tool, the description is largely complete: it names the resource and the exact inclusion scope. It could be slightly richer by mentioning that search_accounts is the filtering alternative, but the absence of an output schema and the low complexity keep the gap small.

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 and the input schema confirms this with 100% coverage. The baseline for zero-parameter tools is 4, and the description correctly adds no parameter details since there are none. There is nothing more to explain.

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 identifies the operation ('List'), the resource ('social media accounts'), and the exact scope ('accessible to the authenticated user, including accounts shared via teams'). This distinguishes it from sibling tools like search_accounts, update_account, and delete_account, which perform different operations or narrower lookups.

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 implies this tool is for retrieving the complete set of accessible accounts, but it does not explicitly state when to choose it over search_accounts or other listing tools. There is no mention of alternatives or exclusion criteria, leaving the usage context implicit rather than explicit.

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