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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. Beyond that the description adds nothing: no pagination behavior, no dataset scope or freshness, no explanation of what 'black-box' means in terms of data visibility. With a mutation-free read tool the bar is lower, but there is still no added context.

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?

A single compact sentence with no padding, which is good structurally. However the brevity comes at the cost of substance: the one clause that could be informative ('black-box public') is the least clear part.

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?

An output schema exists so return values need no explanation, but a 4-parameter paginated read tool with two undocumented parameters and no differentiation from a near-duplicate sibling needs more than one sentence. The agent lacks the information to choose the right tool or to use paging correctly.

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 50%: role and period have enum descriptions, while limit and offset carry no documentation in either schema or description. The phrase 'by canonical role' gestures at the role parameter but neither enumerates the roles nor explains pagination, period windows, or the default of 'overall'/'all'. The description fails to compensate for the coverage gap.

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 verb 'List' and resource 'reputation leaderboard entries' are specific, and 'by canonical role' hints at the grouping. But 'black-box public' is unexplained jargon, and the description never distinguishes this from the sibling kellian_list_leaderboard, which sounds nearly identical. An agent cannot tell which leaderboard tool to pick without opening both schemas.

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?

No when-to-use guidance, no exclusions, and no mention of the alternative kellian_list_leaderboard or reputation getters like kellian_get_agent_reputation. The agent must infer the selection criteria entirely from the name.

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