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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: it takes no arguments and describes the richness of the returned inventory (endpoints, workflows, contract URLs, provenance endpoints). It stops short of describing output format details, so not a full 5.

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?

Front-loaded with the decisive 'START HERE' and 'Takes no arguments' signals. The middle enumeration of return contents is dense but each clause maps to a real category; the parenthetical about the disease-cure landscape is slightly verbose but still purposeful.

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?

No output schema exists, so the description carries the burden of explaining return values, and it does so thoroughly (endpoints, tool names, workflows, contract URLs). Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description confirms 'Takes no arguments', matching the empty schema, which removes any ambiguity about invocation.

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 specific verb+resource (list the server's capabilities) and precisely enumerates what the inventory contains: HTTP endpoints, MCP tool names, research workflows, and contract URLs. The opening 'START HERE' immediately distinguishes it from all sibling tools as the discovery entry point.

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?

Gives an explicit condition for use ('if you do not yet know what this server can do') and an explicit trigger ('Call this before guessing an endpoint or a parameter name'). This is exactly the when-to-use guidance an agent needs to route to it ahead of the many get_*/list_* siblings.

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