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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the four distinct data categories returned and stating the required permission scope (analytics:read), which the annotations do not convey. No mention of rate limits, caching, or freshness semantics for 'current' metrics.

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 tightly written sentences with zero filler: the data scope comes first, the permission requirement second. Every clause carries information an agent can act on.

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?

With an output schema present, the description need not explain return values, and it correctly focuses on scope and authorization. An agent has enough to invoke the tool correctly, though it lacks any routing hint toward the list-level sibling when the target post is unknown.

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 there is only one parameter, postId, which the schema documents as 'dopost post ID'. The description adds no additional meaning about the identifier's format or where to obtain it, so the baseline 3 for high-coverage schemas 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 ('Read') and resource ('current metrics, cumulative snapshots, collection progress, and external-link availability for one dopost post'), which is far more informative than the title alone. The singular 'one dopost post' implicitly contrasts with the sibling list_post_performance, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

'Requires analytics:read' gives a concrete prerequisite for calling the tool, which is genuinely useful. However, there is no guidance on when to choose this over list_post_performance or get_analytics_overview, and no statement of when it would not apply, leaving the usage context implied.

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