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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It discloses payment requirements (x402, USDC on Base, PAYMENT-SIGNATURE header), data sources (OpenAlex, Crossref), and global coverage. It does not mention rate limits, return formats, or error behavior, but the disclosed details are important and not present elsewhere.

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 longer than ideal, but the bulleted endpoint list and brief coverage line make it scannable. The first sentence has a slightly promotional tone, yet each section conveys necessary information (purpose, payment, endpoints, pricing). It is appropriately structured for a multi-endpoint tool.

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?

The description covers multiple endpoints, payment, and data source, but it does not map parameters to specific actions (e.g., which params to use for 'topic-scan' vs 'literature-brief'). There is no output schema or description of return values. Given the tool's complexity (8 actions, 12 params), this omission leaves meaningful gaps in the agent's ability to invoke it correctly.

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?

Input schema covers 100% of parameter descriptions, providing a solid baseline. The tool description adds value by explaining what each endpoint does (e.g., 'ref-check: Bibliography verification', 'journal: Journal/venue intelligence'), which enriches the semantics of the 'action' parameter and helps interpret related params like 'citations' and 'funder'.

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 clearly states the tool's domain and function: 'Academic citation analytics for AI research agents, grant offices, and PIs' and enumerates specific capabilities (bibliography verification, retraction detection, metrics, impact scans, literature briefs). It distinguishes itself from sibling 'pulse' tools by focusing specifically on academic citations and scholarly infrastructure.

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 description identifies target users (AI research agents, grant offices, PIs) and lists concrete use cases via endpoints, implying when to use the tool. However, it does not explicitly state when not to use it or name alternatives (e.g., other pulse tools for non-academic domains), so it falls short of a 5.

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