recipe_crud_get_one

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

No annotations provided. Description does not state that this is a read-only operation, no side effects, authentication requirements, or rate limits. Simple GET but crucial details missing.

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, front-loaded with 'Get One', no unnecessary words. Highly concise and easy to parse.

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, so description should clarify 'all data' but doesn't. Tool is simple (1 param, read-only) but could mention typical response structure. Adequate but not complete.

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 covers 100% of parameters with description 'A recipe's slug or id'. Description repeats this info without adding new constraints or format details. 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?

Description clearly states it retrieves a single recipe by slug or id and returns all data. It distinguishes from 'recipe_crud_get_all' but not from other similar get tools like 'get_recipe'.

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 this tool over alternatives (e.g., 'get_recipe', 'get_recipe_as_format', 'get_shared_recipe'). Agent must infer from name and siblings.

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