system_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states what information is reported, and the overall tone implies a read-only, safe operation. However, it does not explicitly mention that results are cached by default (only the schema's refresh parameter description implies this) or that no side effects occur. This is a minor gap for a status tool.

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 sentence that front-loads the action and lists the report contents without redundancy. Every word contributes to understanding the tool's purpose.

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 tool is simple, has only one optional parameter, and no output schema. The description sufficiently explains what the tool returns by listing the major categories of information (version, platform, dependencies, available tools). This is complete for a status tool.

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 input schema covers 100% of the parameters (the single 'refresh' boolean) with a clear description, so the baseline is 3. The tool description does not mention the parameter or add any additional semantics beyond what the schema already provides.

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 uses a specific verb ('Report') and resource ('1PDF MCP') and explicitly lists the items reported (version, platform, optional dependencies, available tools). This clearly distinguishes it from the many sibling tools, which all perform document conversions or manipulations.

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 makes the tool's context obvious as a system status utility without needing an explicit 'use when' statement. No sibling tools serve a similar purpose, so there are no alternative tools to exclude. The only minor gap is that it doesn't explicitly say to use this tool when you need to check availability or diagnose issues, but this is strongly implied.

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