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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description reinforces the open-world nature ('public job market') but says nothing about visibility lifetime, whether the post can be edited/closed, or cost — details meaningful for a non-idempotent public mutation.

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 front-loaded sentence with no filler, and the field list doubles as a quick parameter cue. It is efficient but borders on under-specification rather than being genuinely tight.

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 7-parameter, non-idempotent public mutation with zero schema coverage and no output schema, the description is too thin. It leaves required-vs-optional (only title required), tag semantics, deadline format, and post-creation behavior unexplained.

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 0% across 7 parameters, so the description must compensate. It conceptually maps 'what' (title/body), 'how many' (qty), 'budget', 'deadline', and 'where', which helps, but leaves 'tags' and the title/body split ambiguous and gives no format hints (deadline string format, budget currency).

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?

A specific verb plus resource ('Post a need to the public job market') with the key field concepts spelled out. It does not name or distinguish itself from plausible siblings such as task_post, offer_post, or listing_create, so an agent still has to infer which posting tool is which.

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?

'public job market' and 'need' imply the usage context (open, hiring-style request) but there is no explicit when-to-use/when-not guidance and no alternative named. The selection between this and task_post/offer_post is left to inference from the name alone.

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