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_suppliers]
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| account | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. Description adds that params are passed as JSON in 'data' but creates confusion by listing unrelated actions. Does not clarify behavior specific to list_suppliers.
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?
Description is long and includes a list of actions not relevant to this tool. Could be shortened to 'List suppliers. Pass parameters as JSON in data field.' Wastes space.
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, no description of return format or filters. Tool is a simple list but description provides no useful context beyond the name.
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%, so description must compensate. Only says 'All params passed as JSON in data field' – no explanation of what params list_suppliers expects or what account is for. Adds no meaningful semantics.
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 opens with generic 'Read financial data' instead of stating specific purpose. Lists many actions including list_suppliers, then notes flattening to list_suppliers, but does not clearly state what this tool does. Vague and 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 list_suppliers vs sibling tools like search_supplier. Does not specify prerequisites or 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.