Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent. Description adds specific behavioral details about return values in different credential states, which enhances transparency 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?
Two sentences, no filler. Purpose stated first, then conditional behavior. Every sentence adds value.
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?
Covers the two main scenarios and explains output fields. No output schema, but description fills the gap. Could mention data format (JSON) but not essential.
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?
No parameters exist, so schema coverage is 100%. Description explains return values, which is the relevant information for a parameterless tool.
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?
Clearly states it returns connection status and URLs. Distinguishes between authenticated state and missing credentials state. Sibling 'authenticate' implies this is a status check, not the action.
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?
Implies usage for checking connection status, but does not explicitly compare to sibling 'authenticate' or state when not to use. The description covers both possible states, giving clear 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.
Each iFood-specific tool targets a distinct resource (catalog, availability, financial summary, store, order detail, order list, transactions). The generic platform tools (authenticate, connect, marketplace, etc.) are also distinct. The only slight overlap is between connect and authenticate, but their descriptions clearly separate connection status from token-based login.
Names are all snake_case but follow mixed patterns. The iFood tools use a consistent 'ifood_vendas_' prefix followed by nouns or noun phrases (cardapio, disponibilidade, financeiro_resumo, pedido_detalhe). Platform tools use imperative verbs (authenticate, connect, report_bug) or descriptive names (toolkit_info). No uniform verb_noun convention exists across the set.
13 tools is within a reasonable range, but 6 of them (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are generic platform utilities unrelated to iFood. This makes the server feel like a mixed bag rather than a focused iFood integration, reducing appropriateness for the server's stated purpose.
The iFood tools cover read-only workflows: catalog, availability, financial summary, store data, order listing, order detail, and financial transactions. However, there are no write operations (e.g., update menu, cancel order) and no search/filter capabilities beyond basic period-based listing. Core read operations are covered, but the surface is incomplete for full lifecycle management.