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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it returns supported formats/restrictions and does not guarantee social network acceptance. It does not describe pagination or freshness, but output schema coverage reduces that need.

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 front-loaded and four sentences long, with each sentence serving a purpose: purpose, return contents, usage timing, and caveats. The sentence about requirements varying by network slightly repeats the earlier scoping idea but remains useful context.

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?

Because an output schema exists and annotations cover safety/idempotency, the description need not explain return values or side effects in detail. Still, the key gap is the mismatch between 'specific social network and account type' and an empty input schema, leaving the agent unsure how the target is supplied.

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 and the schema explicitly disallows additional properties. However, the description repeatedly refers to 'a specific social network and account type,' implying selectors that do not exist in the input schema. This creates a false expectation about how the target is specified.

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 gives a specific verb and resource: 'retrieve publishing requirements and capabilities' for a social network/account type. It also distinguishes itself from publishing tools by stating it 'does not publish content,' though it does not clearly differentiate from networks.list.

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?

It explicitly says to use the tool 'before publishing to check whether the requested content is supported' and clarifies that it does not publish or guarantee acceptance. This gives a clear when-to-use condition and boundary against posts.publish_post.

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