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

No annotations are provided, so the description must fully disclose behavior. It only lists a few features and does not explain query semantics, response structure, limitations, required authentication, or what 'influence' means. The description adds almost no behavioral context beyond the tool's name.

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 extremely short, but this is under-specification rather than effective conciseness. It lacks a clear structure or front-loading of key operational information. While every word may earn its place, there are far too few words to be useful.

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?

Even though an output schema exists)Skip, the tool has one optional parameter, and the description gives no clue about how to supply the query or what output to expect. It is completely inadequate for an agent to invoke this tool correctly. Complexity is low, but the description is still far from 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?

The input schema has one parameter 'q' with a default value but no description, and schema coverage is 0%. The description does not explain what 'q' represents (presumably a query string). The parameter's meaning is left entirely to inference, which is inadequate.

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 the resource (Semantic Scholar) and hints at capabilities (Paper TLDR, citations, influence), but lacks an explicit verb like 'search' or 'lookup'. It is a noun phrase, so an agent can infer it deals with academic papers, but it's not clear whether this tool fetches paper details, runs a search, or computes metrics. It does not strongly distinguish itself from similar scholarly siblings like arxiv or pubmed.

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 guidance on when to use this tool versus alternatives. The description does not mention any scenarios, prerequisites, or exclusions. With siblings like arxiv, dblp, openalexwork, and pubmed, an agent has no basis for selecting this specific tool.

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