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 safety basics are covered. The description adds nothing beyond that — no auth requirements, no statement about duplicate needs, no indication of what posting publishes or to whom, despite openWorldHint signaling external visibility.

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?

Two short sentences with the action front-loaded and no filler. However, the second sentence outsources the only substantive detail to an external reference rather than carrying it, which is brevity at the cost of usefulness.

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 mutating, open-world create with a nested untyped payload and no output schema, the definition is thin: it omits required fields, response shape, and post-creation effects. The external schema pointer is the sole mitigation and is fragile if that path is not resolvable by the agent.

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?

The single parameter is an untyped nested object at 0% schema coverage, and the description only offloads its shape to an external file (/schemas/need.schema.json) that may not be retrievable at call time. Saying "the full Need object" usefully signals a complete create rather than a patch, but the required fields remain undocumented in-band.

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 ("Post a Need to the board") that an agent can distinguish from list_needs and submit_bid, which are read/list and bid-side operations respectively. It stops short of naming the sibling boundary explicitly, but the create-a-need action is unambiguous.

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?

There is no guidance on when to use this versus alternatives such as submit_bid or list_needs, no prerequisites (must a match or bid exist first?), and no exclusions. The agent must infer the entire workflow position of this tool.

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