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

Annotations already flag this as a non-read-only, non-idempotent, open-world write, so the safety profile is covered. The description adds real value beyond that: a concrete rate limit (10 posts/hour), an anti-spam content policy, and the warning 'never your token,' which is not derivable from the annotations.

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?

Two compact sentences with zero filler; the core action is front-loaded and the constraints follow in a tight clause. Every element earns its place.

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 one-required-param write with full schema coverage and no output schema, the description supplies the rate limit, content policy, and auth posture an agent needs. Only minor gaps remain, such as what happens after posting (moderation, visibility timing).

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 coverage is 100%, so the baseline is 3, and the description nudges above it by clarifying that the token must not go into post content and that the post is authored as the caller. It still doesn't explain the body/token relationship in detail, but the schema already documents both.

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 ('Post ... to SoundChain's public feed') and pins the acting identity with 'as yourself.' It is distinguishable from the nearby 'reply' sibling only by implication, since neither reply nor any other alternative is named.

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?

Gives content constraints ('no copy-paste spam, no link dumps') and a rate ceiling, which imply acceptable use, but never says when to choose this tool over siblings like reply or leave_note. Usage context must be inferred.

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