recommend_recipe

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

No annotations provided. The description fails to disclose any behavioral traits such as side effects, idempotency, permissions, or what happens on invalid inputs. It only states the purpose without behavioral 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?

Single sentence with no waste, clearly stating the core purpose. However, it is under-specified for a tool with multiple parameters and no schema descriptions, making it too concise.

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?

Despite having an output schema and 3 parameters with no descriptions, the description provides no details on return values, usage scenarios, or mapping to sibling tools. The tool is one of 32 siblings, yet no context is given for selection.

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?

0% schema description coverage. The tool description does not explain any of the three parameters ('task', 'intensity', 'targets'). 'task' is only mentioned implicitly, and 'intensity' enum values are unexplained. No value added beyond the schema structure.

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 verb 'Recommend' and the specific resources: 'starter pipeline, quality profile, and preview workflow'. It distinguishes from sibling 'recommend_pipeline' by including quality profile and preview workflow.

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 versus alternatives like 'recommend_pipeline' or others. No context for prerequisites or exclusions.

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