Read clinic company info in Feegow. Actions:
list_units: list all units (matriz + filiais). Optional: endereco, cep.
list_locals: list rooms/locations registered across units.
[Flattened action: list_units]
| Name | Required | Description | Default |
|---|---|---|---|
| cep | No | ||
| account | No | ||
| endereco | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds 'Read clinic company info', but also includes an action (list_locals) that belongs to a separate tool, potentially misleading the agent about behavior.
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 short but includes redundant mention of an action that belongs to another tool. It could be more focused on 'list_units' only, reducing clarity.
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?
With 3 undocumented parameters and no output schema, the description fails to explain what the tool returns or how parameters affect results. It also introduces irrelevant functionality (list_locals), making it incomplete.
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%. The description only notes 'Optional: endereco, cep' without explaining their meaning or usage. The 'account' parameter is not mentioned at all, adding minimal value over the schema.
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 mentions two actions ('list_units' and 'list_locals'), but the tool name indicates only 'list_units'. This blurs purpose and fails to distinguish from the sibling tool 'feegow_company_list_locals'.
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 on when to use this tool vs alternatives. The description does not mention the sibling tool or exclude cases, leaving the agent uninformed about appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.