cook_content

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

No annotations are present, so the description carries the full burden of disclosure. It fails to mention any behavioral traits such as whether the operation is destructive, what it does to the content (conversion, optimization), required permissions, expected duration, or side effects. The timeout_seconds parameter implies potential long runs, but this is not explained.

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 a single sentence, which is concise but lacks structure. It is front-loaded with the main action and platform list but provides no additional sentences for context or parameter details. Every sentence should earn its place; this one does but barely.

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 has two parameters with no documentation and an output schema (unknown content), the description is incomplete. It does not specify prerequisites, expected outcomes, or how to interpret results. The presence of an output schema mitigates some lack of return-value info, but parameter semantics and behavioral context are missing.

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 0%, so the description must compensate but does not. It does not explain 'target_platform' valid values, default behavior, or format, nor does it describe 'timeout_seconds' role or consequences of timeout. The description adds no semantic value beyond the parameter names.

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 'Cook', the resource 'project content', and the target platforms (Windows, Linux, Mac, Android…). It effectively distinguishes from sibling tools like compile_blueprint or build_lighting by specifying the cooking operation for content deployment.

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 usage guidance is provided. There is no indication of when to use this tool versus alternatives, no prerequisites, no exclusions, and no context about preparation steps needed before cooking.

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