List PDF files in the vault

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

Description adds sorting order (newest first) beyond the annotations that already declare readOnlyHint and idempotentHint. No contradictions; the 'Read-only' statement aligns with annotations. Slight redundancy but adds value.

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?

Extremely concise, with key info front-loaded: what it lists, key facts, and usage guidance. Every sentence is valuable and non-redundant.

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?

For a simple read-only list tool with well-covered schema and annotations, the description is complete. It covers purpose, usage context, sorting, and relationship to sibling tools. No gaps.

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 coverage is 100% and parameter descriptions are already informative. Description does not add substantive new meaning beyond what the schema provides (e.g., default value for limit is in schema). Baseline 3 is appropriate.

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?

Description clearly states it lists .pdf files with specific metadata (size, timestamp), distinguishes from siblings like obsidian_read_pdf and obsidian_list_notes, and positions itself as the discovery entry point.

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?

Explicitly tells when to use this tool ('discover which PDFs exist') and when to use the alternative ('before calling obsidian_read_pdf'). Also mentions configuration options (--exclude-glob, --read-paths) and sorting behavior.

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