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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context beyond annotations: the Personal+ requirement and the $0.01 USDC payment flow on Base or Solana through _meta["x402/payment"].

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 three tight sentences with no wasted text. Purpose, prerequisite, account requirement, and payment fallback are front-loaded in a useful order.

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 two-parameter read-only lookup with no output schema, it covers purpose, authentication, prerequisite resolution, and payment behavior well. It still leaves some ambiguity around parameter formats and the exact return structure, but the core invocation context is present.

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 0%, so the description has to carry parameter meaning. It names subject_type and subject_id and says to resolve them with search_subjects, but it does not explain the expected ID format or clarify the enum values beyond the keyword/sector wording.

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 states a specific verb and resource: get RI, RIS, HRI, and paper count for one research topic/keyword/sector. It is clear what the tool returns, but it does not explicitly distinguish this subject-level tool from siblings such as get_element_ri or get_subject_papers.

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?

It gives a clear prerequisite: call search_subjects first to resolve subject_type and subject_id. It also explains the Personal+ account requirement and the pay-per-call fallback via x402, though it does not explicitly say when to choose this tool over sibling research-intensity tools.

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