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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true; the description adds substantial context beyond them: the return value ('Returns the post URL'), the Freedom Pledge content constraints (blocks porn/illegal, flags brand/ethics), the outbound-tier approval behavior (from-now-on vs just-once), and the operational instruction 'Call it on the first clear ask; the card is the yes — do not re-ask in chat.'

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 long but every block carries operational value: routing, approval flow, pledge constraints, and connector troubleshooting. It loses a point for redundancy — the hired-agent routing to send_to_user appears in both the first paragraph and the Routing section.

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?

Complete for a destructive open-world publish tool: return value, approval behavior, connector prerequisite, content constraints, and role-based routing are all covered. Parameter-level details and failure semantics live in the 100%-coverage schema, which is acceptable, and there is no output schema to duplicate the return-URL statement.

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%, and the schema's per-parameter descriptions are already unusually rich (character caps, reshaping vs quoting rules, refusal conditions, unbroken-passage excerpt integrity). The description contributes only marginally ('optionally with a URL' and the return-URL note), so the baseline 3 for full schema coverage applies.

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 states a specific action — 'Publish a short text post (optionally with a URL) to this company's connected X account under the Freedom Pledge' — and scopes it to company identity rather than a personal account. It distinguishes itself from numerous X-related siblings by explicitly routing hired agents to send_to_user intent publish and by contrast with ad, metric, and ingest tools.

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?

Explicit when-to-use ('Use when the operator wants this company to post on X'), when-not-to-use ('Hired agents must use send_to_user intent publish instead'), and named alternatives. The Routing section reinforces this and extends it to a degraded prerequisite case: 'Missing tweet.write → request_connector connector="X / Twitter" (FO-native, not Composio).'

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