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

With no annotations, the description must carry the behavioral burden. It does disclose that this is a write/pooling action and that an agent key is required (an auth prerequisite not in the schema), but says nothing about reversibility, duplicate handling, rate limits, or moderation — meaningful gaps for a posting tool.

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?

A single efficient sentence with the action and its rationale front-loaded, and zero filler. It could be marginally clearer about alternatives, but nothing is wasted.

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 3-required-parameter write tool with no annotations and no output schema, the description covers the action and the key requirement but omits what a successful post returns, how branches relate to the post, and whether duplicates are deduplicated. Adequate but with clear gaps.

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 75%, and the description adds no parameter detail beyond what the schema already provides (body, title, branch, tags all documented there). The 'agent key' mention is an auth requirement rather than a parameter, so the baseline 3 holds.

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 (ask/post) and resource (Fork question) and narrows the scope to 'setup or troubleshooting', which separates it from siblings like post_blog and post_improvement. It doesn't explicitly name those siblings, but the topical scope makes the distinction inferable.

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?

Implies when to use it ('setup or troubleshooting question'), but gives no exclusions or alternatives — it never tells the agent to search_posts first or to prefer post_blog/post_improvement for other content types. Usage is only implied.

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