H-Index

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

No annotations provided, so description must carry behavioral burden. It states return content (MCP manifest, pricing, owner, expiry) but does not disclose error handling, authentication, or side effects. 'Get' implies read-only but is not explicitly stated.

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 with no fluff—every part adds value: verb, resource, example, and return fields.

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 simple single-parameter getter, the description is adequately complete, covering purpose and return contents. Could additionally specify not-found behavior, but overall sufficient given no output schema.

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 covers the id parameter with 100% description, and description adds a concrete example format '0.0.10601198/5' that supplements the schema's 'topic/sequence format'.

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 'listing', and unique qualifier 'by its registry ID' with example. This distinguishes it from sibling tools list_categories and search_registry.

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?

Implies usage when you have a specific registry ID, but does not explicitly mention when to use list_categories or search_registry instead. No explicit exclusions or alternatives.

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

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

Since no annotations are provided, the description carries the full burden for behavioral transparency. It indicates a read-only listing operation but does not disclose return format, pagination, or potential side effects. Given the simplicity of the tool, this is adequate but not rich.

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 a single, clear sentence that fully conveys the tool's function without unnecessary words. It is front-loaded and easily parsed.

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?

Given the tool's simplicity (no parameters, no output schema), the description adequately conveys what it does and its place in the registry search workflow. It could mention the return format, but the listing nature is evident from the description and name.

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?

The tool has zero parameters, so the baseline is 4. The description adds context about the purpose of the categories (for filtering registry searches), which is helpful but not essential for parameter understanding.

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 that the tool lists available categories for filtering registry searches. This distinguishes it from sibling tools like search_registry and get_listing, which serve different functions.

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 implies this tool is used to obtain categories applicable to filtering registry searches, but it does not explicitly state when to use it over alternatives or provide any exclusion criteria. The context suggests a prerequisite step, but that remains implied rather than stated.

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

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

No annotations are provided, so the description carries the burden. It discloses that results are ranked by semantic similarity, indicating a read-only, search-like behavior. However, it does not explicitly state that the tool is non-destructive or discuss other behavioral aspects like trust-tier filtering or flag exclusion, though those are in the schema.

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 sentences, direct, and front-loaded with the action and resource. No redundant information; every clause adds value.

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 search tool with 7 well-documented parameters and no output schema, the description gives a high-level overview of behavior and result orientation. It could better specify what fields each listing contains or how pagination works, but the schema covers parameter semantics, and the description clarifies the ranking aspect.

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% for all 7 parameters, so the baseline is 3. The description does not add additional parameter-level meaning beyond the schema, though it does contextualize the query's role in semantic ranking.

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 searches an H-Index registry and returns ranked listings, using specific verb 'Search' and resource 'H-Index registry'. It distinguishes from siblings by focusing on semantic query-based search rather than fetching a single listing (get_listing) or listing categories (list_categories).

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 implies usage for searching/querying the registry via natural language, but it does not explicitly compare with sibling tools or state when to use an alternative like get_listing or list_categories. There is no 'when-to-use' or exclusionary guidance beyond the implied search context.

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