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

Annotations already signal mutation and destructiveness; the description adds useful behavioral context by stating that the server does not execute the request and that an agent bearer key is required. It does not explain side effects or what happens after publishing, but the added context is meaningful.

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, front-loaded with the core purpose. The execution and authentication caveats are high-signal, and every sentence earns its place.

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?

Relative to the nested data object and large sibling set, the description is too sparse. It omits expected return/confirmation behavior, the meaning of the type enum, topic discovery, and when to choose this instead of create_offer or create_post. The schema covers payload shape, but behavioral and routing context is missing.

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 description provides no parameter-level guidance. With schema description coverage at 0%, it does not compensate by explaining that 'data' requires title and body or how optional fields like tags, type, topic, and summary behave. The nested schema has some field-level descriptions, but the tool description itself adds no parameter semantics.

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 description states a specific action ('publish') on a specific resource ('a request'), and the second sentence clarifies that publishing is decoupled from execution. However, it does not explicitly differentiate this tool from siblings like create_offer, create_post, or create_claim.

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?

The description gives no explicit guidance about when to use create_request versus the many related sibling tools. The note that the server does not execute it implies a use case, but there is no when-to-use, when-not-to-use, or alternative routing.

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