List locally tracked posts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral context beyond these by explaining that the result includes 'canonical post records and content-version digests' and that full bodies are excluded. This gives useful insight into what the response contains.

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?

The description is extremely concise, two sentences that front-load the primary purpose and immediately add a key caveat with a pointer to an alternative. Every word earns its place without wasted elaboration.

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 description covers what the tool returns (canonical post records and digests) and what it omits (full bodies), which is sufficient for a simple list operation. However, it does not address filtering or pagination behavior for the `limit`/`status` parameters, nor clarify what a 'content-version digest' is, but the schema and sibling tool names provide some context.

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 0% and the description does not mention the `limit` or `status` parameters at all. While the parameter names are self-explanatory, the description fails to compensate for the lack of schema descriptions, providing no additional meaning or usage hints.

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 the tool's function: 'List canonical post records and content-version digests.' It uses a specific verb ('List') and resource ('posts'), and immediately distinguishes itself from the sibling `get_post` by noting that full bodies are omitted and directing users to `get_post` for exact content.

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 explicitly provides usage guidance by stating 'This omits full bodies; use get_post for exact content.' This tells users when to use this tool versus the primary alternative, making the intended use case clear.

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