social_account

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

With no annotations, the description carries the full disclosure burden, and it says nothing about whether this makes a live network request, requires pre-configured credentials, is read-only and safe, or what it returns. The only behavioral hint is the word "prove", which suggests verification but is never explained. For a tool with zero annotation coverage this is a substantial gap.

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?

One short sentence with no filler, and the core idea is front-loaded. However, the brevity comes at the cost of substance, so it reads as under-specified rather than efficiently concise.

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?

There is no output schema and no annotations, so the description should explain what the verification returns (handle, account ID, boolean?) and any auth preconditions. It does neither, leaving an agent unable to predict the result or the requirements of the call.

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 0% and the single required parameter "network" is bare and undocumented. The description never mentions the network parameter, its expected format, or valid values, so it fails to compensate for the schema gap. Only the loose notion of "credentials belong to" implies a per-network identity check.

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?

"Prove which account/identity the credentials belong to" points at a specific resource (the account tied to the configured credentials), but the verb "prove" is ambiguous: it is unclear whether the tool returns identity information, performs a validation check, or merely asserts a boolean. An agent gets the general theme but not a concrete operation, so this lands at vague rather than specific.

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?

There is no when-to-use guidance, no prerequisites (e.g., 'credentials must already be configured'), and no mention of alternatives among siblings such as social_networks. A use case (checking identity before posting) can only be inferred, not read.

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