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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description largely restates that with 'Read-only; nothing is posted or changed.' It does add useful scope information – the results are the 'latest' drafts for the founder and carry channel/status/text – but says nothing about ordering, emptiness, or how many exist beyond the limit parameter.

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 short sentences with zero filler; the resource and returned fields are front-loaded and the safety note follows. Every clause carries information an agent needs.

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?

For a simple two-optional-parameter read tool with no output schema, the description covers what is returned and confirms it is non-mutating, which is enough to call it correctly. Minor gaps around ordering and empty-result behavior keep it below 5.

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 100%: both 'limit' and 'project' are fully documented in the schema, including default and resolution behavior. The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

Names a specific resource (post drafts written for the founder) and even enumerates the returned fields (channel, status, text), so the agent can tell this is a retrieval tool rather than the write-oriented siblings like log_update or record_work. The verb itself is only implied by the name, which keeps it from a 5.

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?

Usage is only implied: 'read-only; nothing is posted or changed' indirectly signals this is the inspection counterpart to the write tools, but the description never says when to call it, nor names an alternative such as log_update or recall. No explicit exclusions or prerequisites are given.

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