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

With no annotations, the description carries the full behavioral burden, and it does disclose two non-obvious traits: it returns a need-id, and persistence is 'partial until private ingestion and publication.' The privacy warning is also useful. It omits idempotency, whether the submission is binding or purely advisory in effect, and any auth/rate-limit context.

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 compact sentences with the action front-loaded and no filler. It is terse rather than padded, though the 'advisory need.v1' phrasing is dense jargon that a first-time caller may not parse.

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 single-parameter tool wrapping a complex nested payload with zero schema descriptions and no output schema, the definition leaves major gaps: what a 'need' represents, how it differs from a tournament request, and what fields like requester.kind or priorities actually control. The return value mention is helpful but far from sufficient.

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% for a deeply nested 'need' object with required sub-fields (requester, task_class, schema const) and constrained values (priority 0-1 weights, task_class pattern, latency/cost constraints). The description adds only the schema version name and a sensitivity warning; it explains none of the nested field meanings, so the agent must infer them from raw types.

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 concrete verb and resource: 'Log an advisory need.v1 request.' That is a clear action on an identifiable object and pairs sensibly with the sibling get_need. It stops short of distinguishing itself from request_tournament, the other write-style sibling, leaving the agent to infer the boundary.

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 statement of when this tool should be invoked versus get_need or request_tournament, and no listed preconditions. The 'Do not include personal or secret data' line is a data-handling constraint, not usage guidance. The agent must guess the intended entry point of the workflow.

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