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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) by disclosing price, refund policy, a 10x abuse penalty with deletion, async queuing semantics, and the meaning of the 402 error. It omits only lower-value details such as rate limits or content rules, so a 4 rather than a 5.

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?

Front-loads the purpose in the first sentence, then packs cost, async behavior and error handling into short clauses with no filler. Every sentence carries operational information the agent needs.

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 paid, asynchronous, open-world mutation it covers lifecycle, timing and failure handling thoroughly, and an output schema exists so return values need less prose. The missing piece is guidance on the topics/location parameters, which neither schema nor description explains.

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 only 25%: only body's word count is documented, while title, topics (slug pattern, 1-5 items) and the nested location object are bare. The description adds no parameter meaning at all, leaving real gaps in a 4-parameter tool with nested objects.

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 (submit a story to Yarnhen) plus the moderation step, which distinguishes it cleanly from siblings like browse_posts, get_post and cancel_post. The agent knows immediately this is the write-side of the storytelling flow.

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?

Explicitly routes the agent: check get_policy first, poll get_post with the returned id, and surface account_url to the owner on a 402. It even pre-empts a wrong inference by saying not to assume the job is stuck while queued.

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