Get today's menu

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description should disclose behavioral traits like data freshness, permissions, or side effects. It only states the basic function with no additional context about how the tool behaves (e.g., caching, rate limits, or availability). Minimal transparency.

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?

Single sentence with no fluff, but could be more structured (e.g., 'Returns today's Kanpla menu items. Optionally specify moduleId.'). Still efficient and front-loaded.

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?

For a simple tool with one optional parameter and no output schema, the description is sufficiently complete. It conveys the core function and scope. However, mentioning that moduleId override is optional would improve completeness.

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 description coverage is 100% with a clear description for moduleId. The tool description does not add new parameter information beyond the schema, so baseline 3 is appropriate.

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 the tool returns available Kanpla menu items for today. The verb 'returns' and resource 'menu items' are specific, and the scope 'for today' distinguishes it from get_menu_for_date (other dates) and list_modules (module listing).

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 retrieving today's menu, but no explicit guidance on when to use this tool versus siblings (e.g., 'Use this for today, get_menu_for_date for other dates'). The description relies on naming conventions rather than providing explicit context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.