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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavioral context that results are ranked by likes and limited to a window, but says nothing about result size limits or caps beyond what the schema states, so it only modestly exceeds the annotation baseline.

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 filler. The capability and its sort/scope constraint are front-loaded in sentence one, and the usage trigger follows immediately.

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 two-optional-parameter, read-only list tool with no output schema, the description covers purpose, ranking, scope, and trigger conditions adequately. It could say a bit more about what each returned post contains, but nothing critical to correct invocation 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?

Schema description coverage is 100% and both parameters (limit, window) carry their own descriptions and enum values, so the schema does the heavy lifting. The description reinforces the time-window concept but adds no format or default details beyond the schema. 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 specific verb+resource with an added ranking and scope qualifier: 'List the user's best-performing posts (sorted by likes) in a time window.' The ranking and ownership scoping implicitly separate it from siblings like get_analytics (metrics) and get_post (single post), but no sibling is named outright.

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?

Gives concrete trigger conditions: 'what worked,' 'what went viral,' 'examples of their best content' — an agent can match user intent directly. It stops short of explaining when NOT to use it or which sibling to prefer for adjacent needs (e.g., get_analytics for raw metrics).

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