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 but offers minimal information. It states this is a creation operation, implying it's a write/mutation tool, but doesn't describe what happens upon creation (e.g., whether the agent becomes active immediately, what permissions are granted, or if there are side effects like email notifications). It also doesn't mention authentication requirements, rate limits, or error conditions, leaving significant gaps for a mutation 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. There is no wasted verbiage or redundant information, achieving optimal conciseness for such a straightforward statement.

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 complexity (a mutation tool with 7 parameters), lack of annotations, and 0% schema description coverage, the description is incomplete. While an output schema exists (which might describe the created agent), the description doesn't address critical aspects like behavioral traits, parameter meanings, or usage context. For a tool that creates agents—likely involving permissions and system changes—this minimal description leaves too much undefined for effective agent use.

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 schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what parameters like 'occasional' or 'mobile_phone_number' mean in context, nor does it clarify required vs. optional fields beyond what the schema indicates. However, with 7 parameters and 1 required, the baseline is 3 since the schema provides structure, but the description fails to add meaningful semantics to aid understanding.

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 new agent in Freshservice'), making the purpose immediately understandable. It distinguishes from sibling tools like 'update_agent' or 'filter_agents' by specifying creation rather than modification or querying. However, it doesn't explicitly differentiate from 'create_requester' or other creation tools in the sibling list, which would require more specific context about what an 'agent' represents in Freshservice.

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. It doesn't mention prerequisites (e.g., permissions needed), when not to use it (e.g., for updating existing agents), or how it differs from similar creation tools like 'create_requester' or 'create_group'. The agent must infer usage from the tool name alone without contextual help.

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