get_compression_factsWhat PiPic can compress, the file-size and batch limits, and how the free/Pro monthly allowance for the CLI and HTTP API works. Read this before telling a user what PiPic can do for them.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It is transparent about the tool being an informational reference, listing the topics covered. The absence of any side effects is implicit given the 'facts' nature, and the description does not contradict the tool's behavior.
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 two concise sentences, front-loaded with the key topics and ending with a clear usage instruction. Every sentence earns its place with no redundancy or filler.
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 informational tool with no parameters and no output schema, the description adequately covers what it does and when to use it. It could explicitly state that it returns facts in a structured format, but the current level is complete for the tool's simplicity.
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 tool has 0 parameters, so baseline is 4. The description does not need to add parameter details, and the schema is empty with 100% coverage. No additional parameter semantics are required.
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 specifies the tool's content: compression capabilities, file-size and batch limits, and free/Pro allowances. This distinguishes it from sibling tools like check_image_supported and get_integration_guide by focusing on compression facts and limits.
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 a clear usage directive: 'Read this before telling a user what PiPic can do for them.' This tells the agent when to use the tool, though it does not explicitly contrast it with alternatives or state when not to use it.
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 has a clearly distinct purpose: check_image_supported for pre-filtering, get_compression_facts for reference data, and get_integration_guide for step-by-step instructions. There is no functional overlap between them.
All tool names follow a consistent verb_noun pattern (check_, get_, get_), using clear, action-oriented verbs. The style is uniform and predictable.
With exactly three tools, the server is tightly scoped to its purpose of providing an integration guide. Each tool earns its place and avoids unnecessary bloat.
The tool set covers the full user journey: understanding limits (get_compression_facts), pre-validating images (check_image_supported), and learning integration steps (get_integration_guide). No obvious gaps exist for the stated purpose.