create_composite_curve_table

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

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds substantial behavior beyond them: the existing-asset reuse policy, the fact that unloadable parents are silently skipped and surfaced in missing_parents, and that the result is saved. No contradiction with the annotations, though the reuse semantics sit in mild tension with idempotentHint=false.

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?

Front-loaded with the create-and-save action and its edge cases, and the Returns block is valuable since there is no output schema. Minor redundancy: the prose already lists parent_count/row_count/created/saved, then the Returns block repeats them fully, costing a little space.

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 mutating create tool with no output schema, the description covers creation, reuse, parent-load failure handling, saving, and the full return shape. An agent has what it needs to call it correctly; the only gap is routing guidance toward the sibling curve-table creation tools.

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 coverage is 100% so the baseline is 3, but the description still adds value: it explains that package_path/name form the output location, that parent_table_paths become stacked parents, and that failures among those parents land in missing_parents. This clarifies parameter roles and consequences beyond the schema text.

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?

States a specific verb (creates) and resource (UCompositeCurveTable) plus the defining mechanic: stacking the given UCurveTables as parents and saving. This distinguishes it cleanly from siblings like create_curve_table and create_composite_data_table, so an agent can tell what it produces without opening the schema.

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?

Gives clear operational context for the reuse path ('an existing composite there is reused and only gets parents if it has none') and the failure mode for bad parents. It stops short of naming an explicit alternative (e.g., when to prefer create_curve_table or create_composite_data_table instead), so it is clear context without exclusions.

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