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 mentions 'Filter' but doesn't disclose behavioral traits like whether it's read-only or mutative, permission requirements, rate limits, pagination, or what the output contains. For a tool with no annotations, this leaves significant gaps in understanding its operation.

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 no wasted words. It's front-loaded and appropriately sized for the tool's apparent complexity, making it easy to parse quickly.

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 reduces the need to describe return values), no annotations, and low schema coverage, the description is incomplete. It states the basic purpose but lacks details on usage, parameters, and behavior, 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 schema provides no parameter descriptions. The tool description adds no information about the parameters ('include_agents' and 'query'), such as what the query syntax is or what 'include_agents' means in context. With low coverage and no compensation in the description, it fails to clarify parameter meanings.

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 'Filter requesters in Freshservice' states a verb ('Filter') and resource ('requesters'), but it's vague about what filtering entails (e.g., search, list with criteria) and doesn't differentiate from sibling tools like 'get_all_requesters' or 'filter_agents'. It provides a basic purpose but lacks specificity.

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 such as 'get_all_requesters' (which might list all requesters without filtering) or 'filter_agents' (for filtering agents instead). The description implies usage for filtering requesters but offers no explicit context, exclusions, or comparisons to siblings.

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