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

Annotations already carry readOnlyHint=true and destructiveHint=false, so "Read-only" is redundant, but "Carries NO performance numbers" adds real payload-shape context not present in structured fields. It doesn't mention whether results are ordered newest-first or what fields are returned, which would be the remaining gap.

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 short sentences, front-loaded with the user intent, then the scope, then the alternative. Every sentence earns its place with zero repetition or filler.

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 single-optional-param, read-only list tool with no output schema, the definition covers intent, scope, safety and routing. 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?

There is exactly one optional parameter and schema coverage is 100%, with the default (5) and max (10) already documented in the schema. The description adds no meaning about how limit interacts with the result set, so baseline 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?

States a concrete verb+resource framed as the user question it answers ("what did I post recently?") and pins the payload scope: "Lists what went out and where." It explicitly distinguishes itself from analytics siblings, so an agent can route without opening the schema.

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?

Names both the use case (recent post history) and the exclusion ("Carries NO performance numbers"), then redirects to the correct alternatives: get_post_analytics or list_top_posts. This resolves the single most likely sibling ambiguity.

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