Retrieve all agents in Freshdesk with pagination support to manage and organize support team details efficiently.
Get all agents in Freshdesk with pagination support.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| per_page | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full burden. 'Get' implies a read operation, but it does not explicitly confirm safety, rate limits, or whether pagination is automatic or requires manual page iteration. The phrase 'pagination support' hints at behavior but leaves key details undisclosed.
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?
A single, concise sentence with no redundant words. The description is front-loaded and appropriately sized for a simple list operation.
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?
The description is too sparse given the lack of annotations, output schema, and explicit alternatives. It does not mention the output shape, pagination behavior details, or when to use this instead of search_agents/view_agent, leaving the agent with insufficient context for reliable selection.
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 coverage is 0%, and the description only adds 'pagination support' without explaining the page and per_page parameters. While the schema provides names and defaults, the description does not compensate for the lack of parameter descriptions or clarify their semantics beyond generic naming.
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 ('Get all agents') and resource ('agents in Freshdesk'), which is specific and distinguishable from siblings like view_agent (singular) and search_agents (search). It does not explicitly differentiate from alternatives, but the core purpose is unambiguous.
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 search_agents or view_agent. The description only mentions pagination support, which implies listing behavior, but does not state exclusions or preferred scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.