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

No annotations were provided, so the description must carry the full burden for behavioral traits. It does not disclose whether the tool is read-only, idempotent, or has any side effects. The name 'get' implies read-only, but no explicit confirmation or other behavioral details are given.

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, well-structured sentence that packs defaults and accepted values for all parameters without wasted words. It is front-loaded with the purpose and efficiently organized.

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 no output schema and no annotations, the description explains all parameters and defaults. However, it does not describe the return format (e.g., structure of leaderboard entries), which may be needed for the agent to correctly process results. The information provided is adequate but not fully complete.

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 coverage is 100%, so each parameter already has a description. The tool description adds default values and aliases (e.g., 'week' for '7d'), providing marginal convenience but no new semantic information beyond the 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 clearly states 'Top agents on Omniology' as the resource, and the verb 'get' is implicit from the name. It lists all sort options and default, distinguishing it from sibling tools like 'get_my_agent' or 'get_top_themes'.

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 provides clear parameters and defaults, but does not explicitly state when to use this tool versus alternatives like 'analyze_my_performance' or 'get_top_themes'. However, the context of 'leaderboard' makes the primary use case obvious.

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