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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the return structure, the fact that 'the caller writes them into its own studies directory; the court writes nothing' (i.e., the tool itself is non-writing), and conditional composition paths keyed to the prompt. It stops short of describing permissions, error behavior, or the edit-list output in detail.

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?

Purpose and return shape are front-loaded, which is good, but the text is dense and cryptic, with several sentences that only make sense to someone already steeped in the domain. It is neither padded nor genuinely clear, so it sits at minimally viable.

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?

For a tool with no output schema and three parameters, the description does sketch the returned document structure and the side-effect semantics, which is helpful. However, the conditional branches are named only by opaque labels, so an agent without prior context cannot fully predict the output, leaving the definition incomplete for the tool's complexity.

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 100%, so the schema already documents study, prompt, and example_usda, making 3 the baseline. The description restates the conditional behavior for example_usda ('bakes the native companion ... or NAMES the shipped companion') and prompt routing, but adds little beyond what the schema descriptions already state.

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 opening states a specific verb and resource: 'Compose the study document and return it', then names the shape of the returned document (structuredContent.usda, name, layers). That is enough for an agent to know what the tool produces. It does not, however, reference or distinguish itself from any sibling tool, and the heavy domain jargon ('court', 'plague cut', 'native companion') makes the exact artifact unclear.

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?

Guidance is implied rather than explicit: the description maps prompt content to behavior ('A Franklin avatar prompt composes the guidance stage', 'An Iliad scene 02 prompt composes the plague cut'), which hints at when each path fires. But it never states when to choose this tool versus an alternative, and no sibling or prerequisite is named.

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