Freshservice MCP server

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 states this is a creation operation but doesn't mention required permissions, whether the operation is idempotent, what happens on failure, or what the output contains. For a write operation with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a basic creation operation and front-loads the essential information.

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?

While the description is concise and clear about the basic purpose, it's incomplete for a 5-parameter write operation with no annotations. The presence of an output schema helps (so the description doesn't need to explain return values), but the lack of parameter guidance, behavioral context, and usage guidelines leaves significant gaps.

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?

With 0% schema description coverage for all 5 parameters, the description provides no additional semantic information about what 'category_id', 'department_ids', 'description', 'name', or 'visibility' mean or how they should be used. The description mentions 'under a solution category' which hints at 'category_id' but doesn't explain its purpose or format.

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 action ('Create a new folder') and resource ('under a solution category in Freshservice'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'create_solution_category' or 'create_solution_article', but the specificity of 'folder under a solution category' provides some implicit distinction.

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 no guidance on when to use this tool versus alternatives like 'create_solution_category' (for creating categories rather than folders) or 'create_solution_article' (for creating articles within folders). There's no mention of prerequisites, dependencies, or appropriate contexts for folder creation.

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