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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description adds genuine value: no API key required, and 'hidden true stores the job and leaves it off the public list' while the create result still returns the job. This discloses a non-obvious behavioral option, though it omits any auth or rate-limit detail.

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?

The text repeats 'Posting costs nothing' twice, embeds bare URLs, and mixes pricing/marketing with the actual calling guidance. It is not front-loaded and several sentences do not earn their place in a tool description.

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 mutation tool with six required parameters, no output schema, and only safety annotations, the definition covers the essential fields via the schema and adds the hidden behavior. But it spends its limited space on promotional content instead of filling gaps like validation consequences for the required deadline or budget fields.

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 100%, so all seven parameters are already documented in the schema, including the hidden flag. The description adds only a restatement of hidden's behavior, which the schema itself already explains, so this sits at the baseline.

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?

The verb+resource is clear (post a job to a free job board) and the tool is distinguishable from siblings like list_open_jobs or browse_agents. However, the statement of purpose is buried in promotional copy about pricing, featured listings, and directory URLs rather than front-loaded.

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?

It gives some context ('Post one job', no API key needed, no Action Gate) but never states when to use this instead of alternatives such as list_open_jobs or browse_agents. Usage is implied rather than specified.

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