pdf_help

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

readOnlyHint=true is consistent with a help/discovery operation, and the description goes beyond the annotation by documenting the return contract (success/message/data with tool names, descriptions, and input schemas). It does not mention latency or authentication characteristics, but for a read-only introspection tool the disclosure is solid.

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?

Purpose is front-loaded in the first sentence, followed by a compact return-format block and two concrete examples. The examples earn their place for a help tool since they demonstrate both the no-arg and arg call shapes, though the section could be trimmed slightly.

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?

An output schema exists, so return values need not be re-explained, and the annotation covers safety. The description still supplies the response shape and examples, making the definition complete for a zero-required-parameter help tool; no prerequisites or edge cases are omitted that would block correct invocation.

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% and the single parameter already documents 'Name of a tool to get detailed help for. Lists all tools if omitted.' The description restates this rather than adding syntax or format depth, so the baseline 3 applies.

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 pair: lists available tools and returns usage help for the pdf-mcp server, with an optional drill-down for a single tool. It is unmistakably the meta/discovery tool, distinguishable at a glance from all named siblings like pdf_extract or pdf_export.

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 and worked examples make the when-to-use clearly implied: call with no arguments to enumerate tools, call with tool_name for detailed help. It states the selection condition for the parameter ('Lists all tools if omitted') but does not explicitly frame when an agent should prefer this help lookup over just reading a tool's own schema.

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