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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Get information' which implies a read operation, but doesn't state whether it makes external calls, returns static content, or requires authentication. It also doesn't describe the output format or side effects, leaving significant gaps.

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 front-loads the purpose. There is zero wasted text, and it is appropriately sized for a trivial informational tool. It could be more detailed but remains concise.

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?

Despite the tool's simplicity, the description lacks essential context about the return value. With no output schema and no annotations, the description should clarify what 'information' the user receives (e.g., a list of tools, an overview, or limitations). It also doesn't mention prerequisites or limitations, leaving the agent to guess about the actual output.

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 and the input schema is empty. Per the rubric, the baseline for 0 params is 4. The description doesn't need to explain parameter meanings since there are none, and it adds no unnecessary param info.

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 it provides information about NanciMCP's capabilities for literature review, using a specific verb and resource. It distinguishes from sibling tools that directly search, download, or analyze literature by focusing on the MCP itself. However, 'capabilities' is somewhat vague and doesn't specify what kind of info (e.g., tool list, help text).

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 gives no explicit guidance on when to use this tool versus alternatives. It doesn't mention that this is an intro/help tool or contrast it with the many search/read tools. Usage is only implied by the name and purpose.

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