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

With no annotations provided, the description carries the full burden of disclosure. It honestly states that accounts are for write capabilities, returns specific fields, explains the default account behavior, notes the empty-account scenario, and explicitly says agents cannot complete OAuth. It even mentions cost (0 tokens), offering unusually transparent behavioral details.

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 concise and well-structured: the main purpose is front-loaded, with subsequent sentences covering return values, usage in future calls, the empty-case fallback, and a practical note about OAuth. Every sentence adds valuable information with no 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 zero-parameter list tool, this description is complete. It covers what the tool does, what it returns, how to use the results, what to do when no accounts are connected, and even the URL for the user to connect. The presence of an output schema covers return value details, so the description only enhances the context.

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 baseline is 4. The description adds value beyond the empty schema by explaining how to use the output (user_id/user_name) on future write calls, which indirectly clarifies the tool's role in the broader write workflow.

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's function: listing X (Twitter) accounts connected to the authenticated Vee3 account for write capabilities. This specific verb+resource+scope distinguishes it from sibling tools that handle posts, searches, or user info.

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 for when to use this tool—before write calls—and explains how to use the returned user_id or user_name. It also instructs agents to ask the user to connect an account when none are available, though it does not explicitly state when not to use this tool or mention alternative tools.

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