get_recipe

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

Lacks annotations, so description carries full burden. It discloses return fields and that item IDs are resolved to names, but omits information on error handling (e.g., invalid ID), authentication requirements, or rate limits. Adequate for a simple read operation but not comprehensive.

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, front-loaded with action and resource, then lists returned fields. No redundant words; every part serves a purpose.

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?

Describes return fields and mentions name resolution, which is helpful. Lacks mention of error behavior, but output schema (if present) may cover return structure. Reasonably complete for a simple fetch tool.

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?

Only one parameter (recipe_id) with no schema description. The description adds context by linking the ID to fetching a recipe, but does not elaborate on expected format, range, or behavior for invalid values. Minimal but sufficient given parameter simplicity.

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 clearly states the tool fetches a crafting recipe by ID, listing exact fields (disciplines, rating, output item, ingredients). It is distinct from siblings like get_item, get_skill, and find_recipes_for_item, which target different resources or operations.

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?

Description implies usage when a recipe ID is known but does not explicitly contrast with find_recipes_for_item (which searches by output item) or other fetch tools. No when-not or alternative guidance is provided.

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