mcp-cloudron

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 describes what the tool does (validates storage, dependencies, and schema) and the output (validation report with errors and warnings), which is helpful. However, it lacks details on permissions needed, rate limits, or side effects, leaving some behavioral aspects unclear for a validation tool.

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 appropriately sized and front-loaded, starting with the core purpose and followed by specific checks and output details. Every sentence adds value without redundancy, making it efficient and easy to understand at a glance.

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's complexity (validation with multiple checks), no annotations, and no output schema, the description does a good job by explaining the validation scope and output format. However, it could be more complete by detailing the report structure or error types, which would help the agent interpret results better.

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% description coverage, with the 'appId' parameter clearly documented as 'The App Store ID to validate'. The description does not add any additional meaning or context beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating further.

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 ('validate app manifest'), resource ('app manifest'), and purpose ('before installation (pre-flight safety check)'), distinguishing it from sibling tools like cloudron_install_app or cloudron_validate_operation. It explicitly mentions what it validates, making the purpose unambiguous.

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 clear context for when to use this tool ('before installation (pre-flight safety check)'), implying it should be used prior to installation operations. However, it does not explicitly state when not to use it or name alternatives among siblings, such as cloudron_validate_operation, which might handle different validation aspects.

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