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 of behavioral disclosure. It states the action 'List all members', implying a read-only operation, but doesn't specify whether it requires authentication, returns paginated results, includes nested data, or has rate limits. This leaves significant gaps for a tool with no annotation coverage.

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 front-loaded with the core action and resource, making it easy to understand at a glance.

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) and only 1 parameter, the description is minimally adequate. However, with no annotations and low schema coverage, it lacks behavioral details like authentication needs or result formatting, leaving room for improvement in context.

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 tool has 1 parameter with 0% schema description coverage, meaning the schema provides no details about 'group_id'. The description doesn't explicitly mention parameters, but it implies the need for a 'requester group' identifier, adding some context. However, it doesn't specify format, constraints, or examples, so it doesn't fully compensate for the lack of schema documentation.

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 verb 'List' and the resource 'all members of a requester group in Freshservice', providing a specific action and target. However, it doesn't explicitly differentiate from sibling tools like 'get_requester_groups_by_id' or 'filter_requesters', which might retrieve related data but with different scopes or methods.

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, such as 'filter_requesters' or 'get_requester_groups_by_id'. It lacks context on prerequisites, exclusions, or specific scenarios where listing group members is preferred over other retrieval methods.

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