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

No annotations are provided, so the description carries the full burden. 'Open reads' hints at a read-only, likely unauthenticated operation, but this is cryptic and unsupported. Nothing is said about return shape, ordering guarantees, or whether results are scoped to a workspace/team.

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?

Very short and front-loaded, with the ranking concept stated first. The opening rhetorical question is a slight inefficiency over a direct statement, but overall there is little wasted text.

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 annotations and no output schema, the description should do more of the behavioral and return-value work. It covers the core purpose and a use hint, but leaves ordering, scoping, and read-safety under-specified for a tool with two optional parameters.

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%, so the schema already documents both 'by' (with enum meaning) and 'limit' (default 20). The description's 'by credit or verified pitfalls' merely restates the enum, adding no syntax or format meaning 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?

The description conveys the resource — ranked contributors scored by credit or verified pitfalls — but frames it as a rhetorical question ('Who is most trusted right now?') rather than a clear verb+resource statement. It also fails to distinguish itself from the close sibling query_trust, which an agent could easily confuse with a rankings endpoint.

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?

The phrase 'pick whose experience to adopt' implies a use case (choosing whose experience to rely on), so usage is suggested rather than explicit. There is no direct comparison to alternatives like query_trust or query_experience, and no when-not guidance or prerequisites.

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