table_of_contents

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

No annotations are provided, so the description carries the full burden. It mentions 'clickable entries' but does not disclose whether the original PDF is modified in-place or a new file is created, how existing TOCs are handled, or any other side effects. The optional 'output_name' parameter suggests output behavior, but the description remains silent on it.

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, focused sentence that clearly conveys the core function. It is front-loaded and contains no filler or unnecessary details, making it highly economical.

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?

While the schema covers parameters, the description lacks details about return values, output file handling, and interaction with existing PDF content. Given the tool's potential to modify PDFs, and without annotations or an output schema, the description is insufficiently complete.

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 has 100% coverage with descriptions for all three parameters (file, entries, output_name). The description adds no additional semantic detail beyond what the schema already provides, so it earns the baseline score.

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 a specific action ('Add a table of contents page') on a specific resource ('to a PDF') and highlights a key feature ('with clickable entries'). It distinguishes itself from sibling tools like 'page_number' or 'edit_bookmarks' by focusing on the TOC page creation.

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 guidance on when to use this tool versus alternatives such as 'edit_bookmarks' or 'page_number'. It does not mention any prerequisites, use cases, or exclusions, leaving the agent to infer the appropriate context.

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