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

No annotations are provided, so the description carries the full burden and it only adds 'Nova-linked' as context. It does not state that this is a read-only/non-mutating operation, what auth or scope is needed, whether results are paginated, or why a list operation would take a notification_message parameter.

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 well-formed sentence with no filler, front-loading the verb and resource. It is sized appropriately, though it spends most of its words on the platform list that the schema already supplies.

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 two-parameter read tool with no annotations and no output schema, the description is minimally viable but leaves the notification_message behavior and the overlap with list_twitter_accounts unresolved. Nothing catastrophically missing, but an agent could call it correctly yet misinterpret the reply-failure semantics.

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?

Schema description coverage is 100%, so the baseline of 3 applies; the description's enumeration of platform keys merely restates the schema's own examples. The notification_message parameter — unusual for a read operation and relevant to follow-up reply behavior — is entirely unexplained in the description.

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 Nova-linked social accounts') and scopes it to a single platform, with the valid platform keys enumerated. It does not, however, distinguish itself from the sibling list_twitter_accounts, which overlaps at least partially in purpose.

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 sentence conveys what the tool returns but gives no when-to-use framing, no prerequisites, and no guidance on alternatives — notably list_twitter_accounts appears in the sibling list and is never mentioned or excluded. An agent must infer routing on its own.

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