Order an SEO-optimized blog post (1,200+ words, same-day delivery). Pay $29 USDC on Ethereum mainnet.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email address to receive the post | ||
| topic | Yes | Blog post topic and target keywords | |
| language | No | English |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses key behavioral traits: payment amount, currency, network, delivery speed, and word count. However, it omits what happens after payment and return value.
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?
Single sentence includes all critical information with no wasted words.
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?
Given no output schema, the description does not explain what the agent receives as a result. It also lacks prerequisites like wallet payment. Completeness is adequate but not thorough.
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 67%. The description adds value by specifying 'SEO-optimized' and '1,200+ words' but does not explain parameter formats or constraints beyond schema.
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 it orders an SEO-optimized blog post with specific word count and delivery. It distinguishes from sibling tools like order_competitor_analysis by specifying 'blog post'.
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 implies use for blog posts but does not explicitly state when to use or not, nor does it compare with sibling tools. Guidance is implicit, not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinctly different deliverable (blog post, competitor analysis, market research, technical summary), making it easy for an agent to select the appropriate one.
All tool names follow a consistent 'order_<noun>' pattern, which is predictable and clear.
With 4 tools, the server is well-scoped for its purpose of ordering research reports; not too few or too many.
Covers common report types (blog, competitor, market, technical) but lacks options for custom requests or status tracking, though these are minor gaps for the intended scope.