maestro_execute

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explains the execution process, the multi-agent Trifecta pipeline for higher quality, and the return values including status and design notes. It does not mention error handling beyond 'status: failed' or potential side effects, but overall provides adequate transparency.

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 well-structured with a clear purpose statement, separated Args and Returns sections, and an example. Every sentence contributes value, and the information is front-loaded. The length is appropriate for the complexity of the tool.

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 complexity (three parameters, no output schema, multiple siblings), the description covers prerequisites, parameter options, return values, and includes an example. It lacks details on error conditions beyond 'failed' status and does not explain behavior when the session is not ready, but overall is sufficiently complete for an agent to invoke correctly.

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?

The input schema has 0% description coverage, so the description must compensate. It does so comprehensively: session_id is described as 'Active session ID with a decision ready', use_trifecta explains the multi-agent pipeline, and quality_target provides explicit options with threshold and iteration details. This adds substantial meaning beyond the schema titles.

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 that the tool executes a MAESTRO session decision to generate design output (HTML, CSS, JS). It is distinct from sibling tools like maestro_get_decision (which retrieves the decision) and design_frontend (which may create standalone designs).

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 explicitly requires a decided session before use, mentioning both 'completing the interview' and 'calling maestro_get_decision' as prerequisites. It also details the quality_target options and their implications. However, it does not provide explicit guidance on when not to use this tool or compare it to alternative design tools among siblings.

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