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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description repeats 'Read-only' and adds useful content about the returned indicators and curves, but does not add richer behavioral traits such as sorting, pagination, or limitations.

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 English portion is front-loaded and mostly efficient, but the appended French translation duplicates the same information without adding new meaning. This makes the overall description longer than necessary for an agent parsing it.

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 tool with four parameters, low schema description coverage, and no output schema, the description is incomplete. It hints at returned indicators but does not explain the period parameter, limit behavior, workspace scoping, or the include_trends flag, many of which are essential for correct invocation.

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 only 25%, so the description should compensate for undocumented parameters, but it does not. It mentions 'period' and 'curves' in passing, yet gives no explanation of days, limit, workspace_uuid, or include_trends, leaving most parameter meaning to the raw schema.

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 states a specific retrieval purpose (best performing publications over a period) and explicitly distinguishes it from the sibling get_post_stats for a single known publication. It also names the indicators returned, so an agent can understand the resource without ambiguity.

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?

It provides explicit guidance: 'Use this to rank posts; use get_post_stats for one known publication.' The alternative and the condition that selects it are stated directly, leaving nothing to inference.

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