Freshservice MCP server

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

No annotations are provided, so the description carries the full burden. It only states the action ('Get') without disclosing behavioral traits such as whether it's a read-only operation, error handling for invalid IDs, authentication needs, rate limits, or response format. This leaves significant gaps for a tool with a required parameter.

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 waste. It's appropriately sized and front-loaded, though it could benefit from more detail given the lack of annotations and low schema coverage.

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 has an output schema (which handles return values), low parameter coverage, and no annotations, the description is incomplete. It lacks context on usage, parameter details, and behavioral traits, making it minimally adequate but with clear gaps for effective tool selection and invocation.

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 description must compensate. It mentions 'requester groups' but doesn't explain the 'requester_group_id' parameter—what it represents, valid ranges, or how to obtain it. The description adds minimal meaning beyond the schema's basic type information.

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 'Get requester groups in Freshservice' states the verb ('Get') and resource ('requester groups'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_all_requester_groups' or 'list_requester_group_members'. It doesn't specify whether this retrieves a single group by ID or multiple groups.

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 like 'get_all_requester_groups' (which likely lists all groups) or 'list_requester_group_members' (which might list members of a group). The description implies usage by ID but doesn't clarify prerequisites or exclusions.

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