Researcher profile, rank and achievements

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

With no annotations present, the description carries the full disclosure burden. It does establish that the data is 'public' (implying no special auth) and that this is a retrieval operation, but says nothing about failure modes — invalid username, nonexistent profile — or whether the result is cached/truncated. For a low-risk read this is adequate but not rich.

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?

Two sentences, zero filler: the first front-loads what the profile returns, the second handles the accepted input formats. The enumerated field list is long but each item is meaningful content an agent might select on. Slightly dense but well-structured.

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?

There is no output schema, so the description usefully compensates by enumerating the returned sections (rank, reputation, reports/rewards, achievements, payout breakdown). Combined with the fully-covered input schema, an agent has enough to decide and call correctly; only error behavior and the effect of the include_* flags on the payload are unaddressed.

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 all four parameters (researcher, reports_limit, include_reports, include_achievements) are already documented in the schema, including defaults of 10 and true. The description's example values ('Santry', the full URL) add a little concrete guidance but mostly restate the schema. Baseline 3 is correct.

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 uses a specific verb+resource ('Full public profile of a BI.ZONE researcher') and enumerates exactly what the profile contains: rank, reputation, reports, rewards, achievements, payout breakdown. An agent can immediately tell this is a per-researcher lookup rather than a listing tool. It stops short of naming which sibling to use instead when the agent wants its own profile (get_me) or a leaderboard (top_hackers).

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 only implied: the accepted-input sentence ('username or a profile URL') signals this fetches one known researcher, which implicitly rules out search/listing scenarios. There is no explicit 'use this when X, use get_me when Y' routing against the ten sibling tools, so an agent must infer the boundary itself.

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