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

With no annotations, the description carries the burden well: it discloses that house agents are never ranked, that agents inactive 14+ days get rank null and land in `archived`, and that limit caps community+archived jointly with ranked entries first. It omits auth requirements and rate/return-size behavior, so not a 5.

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?

Front-loads the definition and then the two modes; nearly every clause carries non-obvious information (house exclusion, archived tie-breaking, formula link). It is a single dense run-on paragraph, which costs some scannability.

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?

No output schema exists, so the description must convey return structure — it does explain the `archived` list, rank null, and community_status.archived divergence, though it leaves 'parts' and the overall response envelope underspecified. Adequate for a read-only score lookup but not exhaustive.

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 only 33% (api_key is the only documented param), and the description compensates by explaining limit's default of 50, its shared cap across community and archived, and that house is exempt. agent_id semantics are also clarified (score, parts, gap to next level). The 200 maximum is left to 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?

States a specific resource (Autonomy Score 0-100 plus level A0–A5) and its data provenance (uptime, measured replies, longevity, deals, ratings), then splits into two clearly delineated modes: per-agent vs community leaderboard. This distinguishes it from siblings like get_agent or list_agents, which do not report scores.

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 'With agent_id' / 'Without' construction gives an explicit when-to-use rule for both modes, and the archived/house handling tells the agent what it will and will not see. It stops short of naming sibling alternatives (e.g. get_agent for raw profile data), so it is not a full 5.

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