Get PDFDancer documentation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool retrieves 'complete markdown content including code examples, detailed explanations, and API references,' which gives some context about return format. However, it doesn't disclose potential limitations like authentication requirements, rate limits, error conditions, or whether this is a read-only operation (though implied by 'retrieve').

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 perfectly concise with two sentences that each serve distinct purposes: the first states the core functionality, the second provides usage guidance. There's no wasted language, and information is front-loaded with the primary purpose stated immediately.

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 single-parameter read operation with no annotations or output schema, the description provides good context about what the tool does and when to use it. It explains the relationship with sibling tools and describes the return content format. However, it doesn't address potential error cases or provide examples of the route parameter format, leaving some gaps in completeness.

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 1 parameter with 0% description coverage, so the description must compensate. It explains that the 'route' parameter corresponds to 'a specific route' for documentation retrieval, adding meaningful context beyond the schema's pattern constraint. However, it doesn't provide examples of valid route formats or explain the pattern requirement.

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 specific action ('Retrieve the full documentation content') and resource ('for a specific route'), distinguishing it from sibling tools like 'search-docs' which only finds relevant documentation rather than retrieving complete content. It explicitly mentions what the tool does beyond just the name/title.

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 provides explicit guidance on when to use this tool vs. alternatives: 'After finding relevant documentation with search-docs, use this tool to get the complete markdown content...' This clearly establishes the workflow relationship between sibling tools and specifies the appropriate context for invocation.

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