get_pdf_object_tree

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

The description mentions lazy loading, which is a key behavioral trait. However, with no annotations provided, the description carries the full burden. It does not state whether the tool is read-only, what happens if the PDF is malformed, or provide any concurrency or rate limit information. The lazy loading mention is a minimal but useful disclosure.

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 concise sentence with no wasted words. It front-loads the key purpose ('Get JSON representation of PDF object tree') and includes the server context. It is appropriately short for a simple tool.

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?

Given the medium complexity (4 parameters, one sibling tool) and no output schema, the description is minimally complete. It covers the basic purpose and lazy loading but lacks return value expectations, error handling hints, or usage scenarios. The sibling tool is not explained, leaving the agent to guess when to use each.

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%, so the baseline is 3. The description does not add any meaning beyond what the schema already provides; it simply restates the overall purpose. The schema descriptions for each parameter are clear and complete, so the description's lack of additional parameter context is acceptable.

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 states 'Get JSON representation of PDF object tree' which is a clear verb and resource. It distinguishes from the sibling tool 'resolve_indirect_object' implicitly by focusing on the full tree rather than indirect object resolution. The mention of lazy loading adds specificity.

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?

No guidance on when to use this tool versus its sibling 'resolve_indirect_object'. There is no mention of prerequisites, limitations, or alternative tools for different use cases. The description does not help the agent decide between this and related tools.

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