Read financial data in Feegow. Actions:
list_suppliers, search_supplier, list_categories, list_cost_centers, list_transfers, list_invoices, list_current_accounts, find_invoice_nfse, list_credit_card_brands, list_vouchers, list_sales, list_private_tables, get_dmed. All params are passed as JSON in the "data" field.
[Flattened action: list_cost_centers]
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| account | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds only 'Read financial data', which is consistent but provides no additional behavioral context beyond annotations.
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?
Wasteful: includes a long list of unrelated actions that are irrelevant for this specific tool. Could be concise by focusing only on list_cost_centers.
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?
No output schema and simple parameters, but description fails to specify what the tool returns or how to properly invoke it. Incomplete for agent decision-making.
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?
Input schema has two parameters (data, account) with 0% schema description coverage. Description does not explain their meaning or usage, leaving the agent without guidance.
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?
Description is generic: 'Read financial data in Feegow' and lists many actions including list_cost_centers, but does not explicitly state that this tool lists cost centers. Purpose is vague and nearly tautological.
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 lumps multiple actions together without differentiation.
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.
Many tools have identical descriptions (e.g., multiple tools with same 'Read appointments and scheduling data' text) and only differ by a 'flattened action' label, making it impossible for an agent to distinguish which tool to call for a specific operation.
Names follow a loose verb_noun pattern but are extremely inconsistent: some use underscores, some have redundant prefixes like 'feegow_appointment_', and the same actions are duplicated across multiple tool names (e.g., 'list' appears in many). The 'flattened action' suffix is confusing.
94 tools is far too many for a clinic management system. This is clearly due to a one-action-per-tool design that fragments the API surface, making the server bloated and hard to navigate. A typical well-structured server for this domain would have 10-20 tools.
The server covers many areas (appointments, patients, financial, procedures, stock, etc.), suggesting broad functionality. However, the fragmentation obscures gaps and makes it difficult to determine if all CRUD operations exist for each entity. Some areas (e.g., stock write) have multiple tools for single actions.