convert_schematic_pdf

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 discloses that the tool saves raw, semantic, and final JSON artifacts, which implies file-writing side effects. However, it does not state whether it overwrites files, what error handling occurs, or whether it is idempotent, leaving important behavioral details unclear.

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 that states the action and outcome without extraneous words. It is front-loaded and efficient, though it uses jargon ('four-layer baseline') that could be expanded. Overall, it is appropriately sized.

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 has two parameters, no output schema, and no annotations, yet the description gives only a high-level summary. It does not explain the meaning of 'four-layer baseline', what the JSON artifacts look like, or how the pages parameter affects conversion. For a tool with siblings, this lacks sufficient context for reliable 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?

The description provides zero information about the input parameters. With 0% schema description coverage and no mention of source_path or pages in the description, the agent has no understanding of what parameters mean or how to populate them. The description completely fails to compensate for the schema gap.

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 the tool runs a conversion and saves specific JSON artifacts. The verb 'Run' combined with 'conversion' and the tool name 'convert' make the purpose clear. It distinguishes from siblings ('inspect' and 'validate') by indicating a conversion/output-producing step, though it does not explicitly compare to them.

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?

There is no explicit guidance on when to use this tool versus the sibling tools. The mention of 'baseline conversion' implies a standard conversion process, but no prerequisites, exclusions, or alternative references are provided. Usage is only implied by the tool's name and general function.

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