calculate_pasta_portions

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the tool calculates quantities but does not describe output format, error handling, or assumptions (e.g., standard serving sizes). The presence of an output schema mitigates this somewhat, but the description could add more context.

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 extremely concise: two sentences clearly convey the tool's purpose and a helpful reference to related tools. Every sentence adds value, with no redundancy.

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?

Given the tool's simplicity and the presence of a detailed input schema and output schema, the description is adequately complete. It covers the primary function and hints at related tools. Minor gaps (e.g., no mention of measurement units) are compensated by schema details.

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 coverage is 100% with detailed descriptions for each parameter. The description adds minimal extra meaning beyond 'given number of people' for num_people. Baseline 3 is appropriate as the schema already effectively documents parameters.

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 clearly states the tool's purpose: 'Calculate dry pasta, water and salt for a given number of people.' It uses a specific verb ('Calculate') and resource ('dry pasta, water and salt'), and distinguishes itself from siblings by referencing 'cuisine' calculators and pointing to list_bundles for related tools.

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?

The description provides clear context for when to use this tool (pasta portion calculation) and directs users to list_bundles for related calculators, implying these are alternatives. However, it does not explicitly state when not to use it or list exclusions.

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