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 fails to do so. It doesn't indicate whether this is a read-only or mutating operation, what permissions are required, how the note affects the ticket, or any rate limits/error conditions. This is inadequate for a tool that presumably creates data.

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's appropriately sized and front-loaded with 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?

Given the tool's complexity (a creation operation with 2 parameters), lack of annotations, and presence of an output schema, the description is incomplete. It doesn't explain behavioral aspects, usage context, or what the output might contain, leaving significant gaps for the agent to understand how to properly invoke this tool.

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 description provides no parameter information beyond what's implied by the tool name, and with 0% schema description coverage, the schema only documents parameter names and types. However, since there are only 2 parameters (ticket_id and body), their purpose is reasonably inferable from context, meeting the baseline for minimal parameter count.

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 note') and target resource ('for a ticket in Freshservice'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'send_ticket_reply' or 'update_ticket_conversation' that might also involve ticket communication, which prevents 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, constraints, or when to choose this over similar tools like 'send_ticket_reply' or 'update_ticket_conversation', leaving the agent without usage context.

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