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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-annotated context: the required read_private_leaderboards OAuth scope and the underlying GET /users/current/leaderboards endpoint.

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 terse sentences with no waste, the resource and returned fields front-loaded before the scope and endpoint details. Slightly dense but every clause carries information (fields, auth, endpoint).

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 no output schema, the description usefully enumerates the return fields, and the auth scope plus endpoint disambiguate the call. Pagination is handled by the schema, so the only remaining gap is differentiation from the singular sibling.

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 the single page parameter is fully documented in the schema, including the next_page chaining hint. The description adds no parameter detail beyond that, so the baseline 3 is appropriate.

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 the resource precisely and even enumerates the returned fields (id, name, time range, member count, edit rights), so the agent knows exactly what data comes back. It does not differentiate itself from the singular sibling wakatime_get_private_leaderboard, which is a meaningful ambiguity in this tool set.

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?

Usage is implied by 'the private leaderboards the user is in', and the OAuth scope prerequisite is stated, but there is no explicit when-to-use or when-not-to-use guidance and no routing to the singular get_private_leaderboard alternative.

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