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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description need not restate it. It adds real value by disclosing the return contents and the cross-tool linkage of account_id, though it says nothing about behavior when no profiles are connected or about ordering.

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, front-loaded with the resource and return fields, then the trigger, then the downstream linkage. Every sentence earns its place, though the account_id sentence is slightly redundant with the field enumeration in the first sentence.

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 read tool with no output schema, the description carries the whole load and does so: it says what is returned, which fields matter, when to call it, and how the ids are consumed downstream. Nothing an agent needs to invoke it correctly is missing.

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 no parameters, so the baseline is 4. The description correctly adds no parameter detail, and its mention of account_id describes an output field rather than an input, which is the right thing to clarify for a zero-argument tool.

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?

States a specific resource (Twitter and LinkedIn profiles connected to the VoiceMoat account) and enumerates the returned fields (account id, handle, display name, default platform). It is clearly distinguishable from every sibling, none of which list connected accounts.

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?

Gives an explicit trigger: 'Use when the user asks which profiles are connected or which one they are on.' It also routes downstream by noting account ids are what publish_post and schedule_post consume. It stops short of naming a when-not-to-use or a competing alternative, so it is clear context rather than full routing guidance.

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