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

With no annotations, the description carries the full burden. It does disclose two things structured data does not: the credit cost (1 credit) and the shape of the returned fields, which is meaningful for a paid call. It says nothing about result ordering, pagination/total counts, rate limits, or error behavior, so the mutation/consumption profile is only partially covered.

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 compact clauses, front-loaded with the action and resource, then return fields, then cost. No filler or restatement of the name.

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 4-parameter read tool with no output schema and no annotations, enumerating the returned fields plus the credit cost covers most of what an agent needs to decide and call. The remaining gap is behavioral detail around result limits and source-specific differences, which the description leaves entirely implicit.

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 are already documented, making 3 the baseline. The description adds one genuinely new fact not in the schema: that source defaults to OpenAlex. It adds nothing about limit's interaction with totals or the year-range semantics.

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 verb+resource ("Search scholarly papers") and enumerates what comes back (authors, venue, year, DOI, citations, open-access link), plus the two underlying sources. It does not name or contrast with any sibling (arxiv_search, pubmed_search, doi_lookup), so the agent must infer the boundary itself.

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 only usage signal is that OpenAlex is the default and Crossref is the alternative source. There is no statement of when to pick this over arxiv_search, pubmed_search, or doi_lookup, and no exclusions or prerequisites.

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