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

Annotations already flag this as a destructive, idempotent, open-world write. The description adds real value beyond them: it re-validates source, destination, platform consent and connection before committing, and it explains the ambiguous-acceptance recovery path ('recover from the existing receipt; never blindly repost'), which coherently explains the idempotentHint. What is missing is any statement of what a failure or receipt actually looks like or what permission level is required.

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 short sentences with no filler, and the gating constraint is front-loaded. But the compression comes at the cost of clarity: 'Admit', 'proposal', and 'receipt' are internal vocabulary used without definition, so density here reads as cryptic rather than efficient.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Still, for a destructive, open-world publication commit with two entirely undocumented required parameters, the description leaves out the single most important thing an agent needs: where proposal_id and request_key come from and how to obtain them.

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 neither parameter is named in the description. 'Matching approved proposal' faintly implies proposal_id, and 'existing receipt' faintly implies the idempotency role of request_key, but an agent must guess at the format, origin, and uniqueness requirements of both required fields.

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 verb 'Admit' is unusual and the resource ('approved proposal') is never tied back to a social draft being scheduled. Native publication/scheduling is mentioned only as a precondition check, so the agent must infer that this tool actually commits an approved draft to a social platform. It does not distinguish itself from nearby siblings such as publish_social_draft, prepare_social_schedule, or native.social_schedule_draft.

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?

'Admit only the matching approved proposal' implies a gating precondition (a draft must already be approved), which is useful context. However, no alternative is named and no when-not guidance is given, so an agent cannot tell from the description why it should call this instead of publish_social_draft or prepare_social_schedule.

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