Convert S3 Markdown File to PDF

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

No annotations are provided, and the description only states the core conversion action without disclosing any side effects (e.g., whether the file is uploaded back to S3, credential requirements, or output handling). It fails to describe behavior beyond the literal conversion, leaving the agent without information about potential permissions or network dependencies.

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 front-loads the action and resource. It contains no filler or redundant explanation, making it highly scannable.

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 tool has seven parameters, nested objects, and no output schema, the description is sparse. It doesn't mention the uploadToS3 behavior, default region, or any distinctions from sibling tools, which are important for correct selection and invocation. The schema covers parameters, but the description lacks contextual depth beyond the basic conversion.

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 all 7 parameters described, so the baseline is 3. The description adds no extra parameter information beyond mentioning bucket and key, which is already in the schema. It does not clarify the format/margin parameters or outputPath semantics.

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 uses the specific verb 'Convert' with clear source ('markdown file from S3 bucket') and target (PDF), and explicitly mentions bucket and key parameters, distinguishing it from sibling tools like convert_markdown_to_pdf which likely handle non-S3 sources.

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 implies that this tool is for S3-hosted markdown files, but it does not explicitly state when to use it over sibling tools like markdown_content_to_pdf or convert_markdown_to_pdf, nor does it provide exclusions or prerequisites. This is only implied usage, not clear guidance.

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