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

With no annotations, the description carries the full burden, and it does disclose the return payload shape and the cost ('Free · 2 credits'), which is genuinely useful. It omits how an org is identified, what happens for an unknown org_key, whether results are cached, and how the 30-day delta is computed.

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?

A single dense sentence plus a cost tag — no wasted words, and the most useful information (what you get) comes first. The noun-phrase opening ('A lab or company's output') is slightly less crisp than a verb-led statement but remains clear.

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?

For a 2-parameter tool with no output schema and no annotations, the description covers the return values and cost well but leaves the required identifier undocumented and gives no routing guidance against related tools. An agent could call it, but would likely have to guess at org_key format.

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% for two parameters, so the description must compensate and largely does not: org_key (the required identifier) is never mentioned, and its expected format is unexplained. Only indirectly does 'top authors' and 'recent papers' hint that 'limit' controls how many entries come back.

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 names a specific resource (a lab or company profile) and enumerates the concrete outputs — paper counts, GitHub stars with 30-day delta, top authors with h-index, recent papers — so an agent knows what it retrieves. It lacks an explicit verb and does not differentiate itself from siblings like 'author' or 'entity_trends', which keeps it below a 5.

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?

There is no when-to-use guidance at all: nothing says whether this is for evaluating an organization's research output versus a single author, nor are any alternatives named. The only implicit cue is the 'lab or company' scope, from which the agent must infer applicability.

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