Create a Post

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

Annotations provide only readOnlyHint=false and openWorldHint=false; the description adds critical behaviors like the rate limit, linking requirements, and implicit write nature, which fully compensates for lack of annotation 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?

One concise paragraph with clear structure: main purpose, type guidelines, special cases, limit. No redundant information.

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?

With 15 parameters and no output schema, the description covers all key usage contexts: type selection, required fields per type, rate limits, and optionality of parameters like agent_id.

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 coverage is 100%, baseline 3. Description adds semantic value beyond schema by grouping parameter requirements by post type (e.g., solutions need parent_post details, ads need entity_id), aiding correct invocation.

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 clearly states 'Publish a post to the NaN Mesh trust network' and elaborates on each post type ('article' for field notes, 'question' for responses, etc.), distinguishing it from sibling tools like get and list.

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?

Explicitly tells when to use each post type, which required parameters are needed for solutions (parent_post_slug or parent_post_id) and ads/spotlights (linked_entity_id), and mentions the rate limit of 1 post per hour.

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