study_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool creates a study and returns created study info, but does not mention side effects, required state, name collision behavior, or whether it modifies the current model. This is a significant gap for a mutation tool with no annotations.

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 front-loaded with the core action, then provides a structured Args and Returns section. The study-type list is a bit lengthy but earns its place by clarifying the most important parameter. No redundant sentences.

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 3-parameter creation tool with no annotations and no output schema, the description covers what the tool does and the parameter semantics, but omits behavioral context such as prerequisites (e.g., needing an active model or connection), what happens on name conflicts, and whether the study is immediately available. It is minimally adequate but leaves gaps an agent would need to infer.

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 is the only source of parameter meaning. It documents all three parameters: study_type with common type values and their contexts, study_name as optional name/tag, and model_name defaulting to the current model. This fully compensates for the schema's lack of descriptions.

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 a specific verb and resource: 'Create a new study in the model.' It distinguishes from siblings implicitly by naming the created entity, but does not explicitly contrast with study_list, study_solve, or others. The added study-type list reinforces the purpose but is not sibling differentiation.

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 offers no guidance on when to use this tool versus alternatives like study_list or study_solve, nor does it state prerequisites such as requiring an active model or connection. Usage is only implied by the verb 'Create'.

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