Freshservice MCP server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention permissions required, whether this is idempotent, what happens on duplicate names, or what the output contains. For a creation tool with zero annotation coverage, this leaves significant behavioral unknowns that could affect agent decisions.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place by establishing the essential what and where of the operation.

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 that an output schema exists, the description doesn't need to explain return values. However, for a creation tool with no annotations, 0% schema description coverage, and multiple sibling tools, the description should provide more context about when and how to use it. The presence of an output schema helps, but behavioral and usage gaps remain significant.

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?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The tool description doesn't mention parameters at all, leaving both 'name' and 'description' completely undocumented. However, with only 2 parameters (one required) and no complex types, the agent can reasonably infer basic usage from the tool name and schema structure alone, meeting the minimum viable baseline.

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') and resource ('a requester group in Freshservice'), making the purpose immediately understandable. It distinguishes this from other creation tools like 'create_agent' or 'create_group' by specifying the resource type. However, it doesn't explicitly differentiate from 'update_requester_group' or explain what a 'requester group' is, keeping it from a perfect score.

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. With sibling tools like 'update_requester_group' and 'add_requester_to_group', there's no indication of prerequisites, when creation is appropriate versus updating, or how this relates to other requester management operations. The agent must infer usage context from the tool name alone.

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