get_metrics

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety/behavior profile is covered and the description need not restate it. The description adds the batch framing ('for a list of bibcodes') but omits practical traits such as the 2000-bibcode ceiling and any rate/latency behavior for large lists.

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 efficient sentence that front-loads the verb and the returned fields with no filler. It is appropriately sized for a two-parameter tool, though it could have spent one clause on the response_format choice.

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?

With no output schema, the description usefully names the returned metric types, which is the main thing an agent needs. However, it is silent on the response_format parameter's markdown/json behavior and the 2000-item input limit, so it is adequate but not complete for a batch tool.

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 50%: 'bibcodes' is documented inline, but 'response_format' (enum markdown/json with default markdown) has no description anywhere. The description reinforces the bibcode-list input but adds nothing about output format selection, so it neither compensates for the gap nor regresses below the baseline.

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 clear verb+resource ('Get citation metrics') and enumerates the return payload (h-index, citation counts, paper statistics), so the agent knows what it gets. It does not explicitly differentiate itself from citation-oriented siblings like get_citations or get_references, which is the only gap.

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 when-to-use guidance, no prerequisites, and no named alternative among the 22 sibling tools. The reader must infer that this is the batch-metrics tool versus get_citations/get_references, and nothing states whether bibcodes must already exist or how many calls are appropriate.

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