List all published essays and fragments: titles, descriptions, prices, and reading URLs. Full text is free for humans at /read/{slug}; machine reads at /essays/{slug} are paid via x402 (USDC on Base).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| essays | Yes | Published essays and fragments. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "essays": {
+ "description": "Published essays and fragments.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "human_url": {
+ "description": "Free full text for humans",
+ "type": "string"
+ },
+ "machine_url": {
+ "description": "Paid machine read via x402",
+ "type": "string"
+ },
+ "price": {
+ "description": "Price in USDC, e.g. $0.01",
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "type": {
+ "description": "fragment, ensemble, or prose",
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "title",
+ "type",
+ "price",
+ "human_url",
+ "machine_url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "essays"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is low, and the description adds genuinely new behavior: human reads are free at /read/{slug} while machine reads at /essays/{slug} incur x402 payment in USDC on Base. That payment gate is exactly the kind of operational constraint an agent needs before invoking.
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 sentences, no waste. The scope and returned fields come first, with the free-versus-paid access model immediately behind it.
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?
An output schema exists, so return values need not be re-explained, and the description nonetheless summarizes the payload. For a zero-parameter, read-only listing tool, nothing an agent needs in order to call it correctly 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 tool takes zero parameters, which sets the baseline at 4. The {slug} references in the description describe returned URL shapes and access paths rather than callable inputs, so no further parameter documentation is applicable.
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 specific verb and resource (list published essays and fragments) and enumerates the returned fields (titles, descriptions, prices, reading URLs). It is clearly distinguishable from a payment-info sibling, though it never names essay_payment_info directly.
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 usage context through the free/paid access model, but never states when to call this tool versus essay_payment_info or what preconditions exist. Guidance is inferable rather than 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.