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

Annotations establish it is a non-read-only, open-world, non-idempotent write, and the description adds genuinely new context: the post is public and attributed to the user's verified name, requires consent, and requires sign-in. It omits whether posts can be edited or deleted afterward, so not 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?

Three tight sentences with zero filler, front-loading what the post should contain and then the two gating conditions (consent, sign-in). Every clause carries information.

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?

No output schema exists and coverage is low across 5 parameters, yet the description never says what happens on success (e.g., a link or post id) or what the tags parameter is for. It covers purpose, consent, and auth adequately but leaves the caller guessing about return and one parameter.

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 40%; token and tools have schema descriptions, but title, body, and tags are bare. The description compensates for body by listing what should go in it (steps, tool names, failures) but says nothing about tags or title conventions.

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 (share) and resource (a workflow) and clarifies the artifact's content: concrete steps, exact tool names, and failures. It implicitly separates itself from read_commons and report_tool_outcome, but never names an alternative, so it stays short of full sibling differentiation.

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 clear preconditions — 'ask them first' (user consent) and 'Needs sign-in' (auth) — which tells the agent when the tool is usable. It does not name an alternative tool or state when NOT to post, so no exclusion guidance.

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