model_get_mpars

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

With no annotations available, the description carries the full burden. The verb 'Get' and the phrase 'with their values' convey a read-only operation that returns parameter data, but the description does not disclose return structure, failure behavior, path requirements, or potential side effects.

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 a single focused sentence with no filler, front-loading the action ('Get all') and the resource ('Model parameters'). Every word contributes to the core meaning.

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 simple one-parameter getter, the description states enough to understand the basic invocation: provide a model path and receive all model parameters with values. However, without annotations, output schema, or parameter details, it is not fully complete for an agent that needs precise path syntax or return shape.

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 schema provides no description for model_path and schema coverage is 0%. The description only indirectly suggests that model_path identifies the model whose parameters are fetched; it adds no detail on path format, required value, or constraints, so it does not compensate for the missing schema documentation.

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 uses a specific verb and resource: 'Get all Model parameters (MPar) with their values.' It clearly states the tool's scope and distinguishes it from mpar_get by emphasizing 'all,' though it does not explicitly name the sibling alternatives.

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?

There is no guidance about when to use this tool versus mpar_get, model_get_mvars, or other related getters. No prerequisites, exclusions, or alternative recommendations are provided, leaving the agent to infer selection from sibling names.

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