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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (id, platform, display name) in the absence of an output schema, and by indicating the ids are reusable identifiers. It does not mention pagination or workspace scoping.

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?

Two short sentences, front-loaded with the identity of the tool and the return fields, followed by the actionable usage hint. No filler or redundant restatement of the title.

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-required-parameter read-only list tool with no output schema, the description covers what it returns and how to consume the ids, which is enough to call it correctly. Minor gaps remain around workspace scoping and whether results are paginated.

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?

There is a single optional 'workspace' parameter whose schema description is present (100% coverage), so the schema carries the parameter documentation. The prose adds nothing about the workspace slug's format or what happens when it is omitted. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource ('List connected social media accounts') and even enumerates the returned fields (id, platform, display name). An agent can distinguish it at a glance from siblings like get_account_stats or get_account_trends, which report metrics rather than enumerate 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?

'Use the returned ids as accountIds when creating posts' gives concrete downstream context, effectively naming create_post as the consumer of this output. However, it offers no exclusions or alternatives (e.g., what to use if you need stats instead), so it stops short of a full when/when-not statement.

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