add_time_parameter

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

All annotations are false and provide no read-only, idempotency, or destructiveness signals. The description only says 'Add' and lists parameters; it does not disclose side effects, prerequisites, default behavior, or whether existing parameters are replaced.

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 compact and front-loaded with the main purpose, followed by a scannable argument list. The bilingual repetition adds some length but does not hurt usability.

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?

The description is adequate for a basic call with one required parameter and sensible defaults, but it lacks context about how this tool relates to materials, functions, or analysis cases, and there is no output schema to clarify return behavior. An agent would need additional knowledge to use it confidently.

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%, and the description compensates by naming all six parameters and adding useful hints such as creep_data format '[[time, value], ...]' and index '-1 for auto'. However, 'time_parameter' is vaguely described as 'Code specific parameters', leaving its exact meaning unclear.

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 states a specific verb ('Add') and resource ('time-dependent material parameters'), and the argument list clarifies that it deals with creep and shrinkage data. It is clear, though it does not explicitly differentiate itself from sibling tools like add_creep_function or add_shrink_function.

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 guidance is provided about when to use this tool versus alternatives such as add_creep_function or add_shrink_function, nor whether this applies to an existing material or creates a new one. The usage context is left entirely to inference.

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