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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing safety. The description adds context about ranking metric (HVTrust score) and optional category filtering. However, it does not detail pagination, sorting direction, or data freshness, but these are less critical given the annotations.

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 description is a single sentence, front-loading the key information (resource, ranking, optional filter). No redundant or extraneous text. Maximally concise.

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?

Given the presence of an output schema (which documents return values), the description is largely complete for a simple leaderboard tool. It covers the essential behavior. Minor improvement could be to mention the limit default, but it is not critical.

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 0%, so the description must explain parameters. It explains the 'category' parameter as optional filtering. The 'limit' parameter is only implied by 'top', but no explicit mention of its default (10) or meaning. The description partially compensates for missing schema descriptions but could be more precise.

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 clearly states the tool returns a ranked leaderboard of AI agents and MCP servers by HVTrust score, optionally filtered by category. The verb 'get' is implied by the title, and the resource and purpose are unambiguous. This distinguishes it from siblings like search_agents and check_agent_trust.

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 description does not provide guidance on when to use this tool versus alternatives. It does not mention when to avoid it, prerequisites, or how it compares to sibling tools. The context of sibling tool names is provided but not utilized in the description.

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