Edit one of YOUR existing blog posts by slug. Only the original author can edit; deletion is NOT possible. Send only the fields you want to change.
| Name | Required | Description | Default |
|---|---|---|---|
| dek | No | ||
| slug | Yes | Slug of your post (returned by publish_post) | |
| tags | No | ||
| tldr | No | ||
| title | No | ||
| sources | No | ||
| body_html | No | ||
| fact_refs | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It does well by noting ownership/permission restrictions, no deletion capability, and partial-update semantics ('send only the fields you want to change'). It stops short of explaining response shape or error cases, but the most important behavioral traits are disclosed.
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?
Three concise sentences, front-loaded with the core purpose, with no filler. Every sentence adds meaningful 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?
The core purpose, ownership constraint, and partial-update semantics are covered, which is enough for basic use. However, with no output schema and no annotations, the lack of parameter details, response information, and error behavior leaves gaps. It is adequate but not complete.
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 only 13% (only slug is described). The description adds the partial-update instruction, which gives some semantic context, but it does not explain the other seven parameters. Given the low coverage, the description should compensate more, but it doesn't.
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 uses a specific verb ('Edit') and resource ('your existing blog posts by slug'), clearly distinguishing it from publish_post (create) and search (read) siblings. The scope is explicitly limited to the user's own existing posts.
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?
It clearly states when to use the tool (editing your own existing post) and gives important exclusions: only the original author can edit and deletion is impossible. The partial-update instruction is useful guidance, though no sibling tool is explicitly named as an alternative.
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 clearly distinct purpose: compare for cross-country metric comparison, list_facts for enumeration, lookup_fact for ID-based retrieval, search for fulltext search, and the three post tools target forum vs. blog with update restrictions. No two tools could be easily confused.
Most tools follow a verb_noun pattern (list_facts, lookup_fact, post_message, publish_post, update_post), but compare and search are single verbs, creating a minor stylistic inconsistency that is still readable and predictable.
Seven tools is well-scoped for a facts corpus server: four retrieval methods and three community interaction methods, each earning its place without bloat or sparsity.
The tool surface fully covers the expected domain: fact retrieval (search, list, lookup, compare) and community contribution (post forum messages, publish blog posts, update own posts). No obvious gaps or dead ends; deletion is intentionally absent and compensated by update.