get_accountCheck the FileToPDF API key and return the plan, remaining conversion credits, and subscription status. Free — costs no credits. Use this to verify the connection works.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and openWorldHint, indicating safe, state-dependent reading. The description adds specific details about what is returned (plan, credits, subscription status) and confirms no cost, consistent with the annotations. No contradictions.
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?
Three short, clear sentences with no wasted words. Purpose is front-loaded and every sentence adds value.
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?
With no parameters and no output schema, the description covers the return values and use case. Could mention how the API key is supplied (probably via authentication), but overall sufficient given annotations and sibling context.
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?
No parameters exist, so baseline is 4 per guidelines. The description does not need to explain parameters.
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 checks the FileToPDF API key and returns plan, credits, and subscription status. It distinguishes itself from sibling conversion tools (convert_file, convert_html, convert_markdown) by specifying it is for status verification and costs no credits.
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 explicitly says 'Use this to verify the connection works' and notes it is free, implying use before conversion tasks. It clearly differentiates from siblings but lacks explicit when-not-to-use or alternative pointers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct input source: convert_file handles files from URLs, convert_html deals with raw HTML strings, convert_markdown processes Markdown, and get_account manages account info. There is no overlap.
All tools follow a clear verb_noun pattern (convert_file, convert_html, convert_markdown, get_account), with consistent verb choice and naming style.
Four tools is well-scoped for the domain: three conversion methods covering common input formats and one account tool. No tool is superfluous or missing.
The set covers the main conversion workflows (file URL, HTML, Markdown) and account management. Minor gaps like direct file upload or advanced formatting options for file conversion exist but do not hinder core functionality.