batch_get_semantic_scholar_authors

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

No annotations are provided, so description must disclose behavior. It only states a maximum of 1,000 IDs, but fails to mention read-only nature, rate limits, error behavior, or what happens with invalid IDs. Minimal behavioral disclosure.

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?

Single sentence that is front-loaded with the action and limit. No wasted words.

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?

Although an output schema exists (covering return values), the description lacks essential context such as allowed field values, prerequisites, and when to choose this batch tool over alternatives. For a tool with no annotations and zero param descriptions, this is insufficient.

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?

Because schema description coverage is 0%, the description must explain parameters. It clarifies that author_ids are Semantic Scholar author IDs, but this is largely redundant with the parameter name. The optional 'fields' parameter is completely unexplained, leaving the agent to guess what values it accepts.

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?

Clear verb ('Get'), resource ('authors'), method ('by Semantic Scholar author ID'), and scope ('multiple', max 1,000). Distinguishes from single-author and paper batch tools by explicitly limiting to authors.

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?

No guidance on when to use this versus alternatives like get_semantic_scholar_author_details or batch_get_semantic_scholar_papers. The only implied usage is that it is for multiple author IDs, but no exclusions or alternative recommendations are provided.

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