AxModelFitter_get_fitting_examples

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

The description states it 'Returns ready-to-use templates' with specific contents, implying a read-only operation. However, with no annotations provided, it does not explicitly disclose the absence of side effects, authentication needs, or rate limits. The description could be more transparent about the tool's safety profile.

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 concise, using 7 lines to convey purpose, contents, and usage instruction. It front-loads the main action ('Get complete working examples') and lists features concisely. Every sentence adds value, though it could be slightly more streamlined.

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?

Given the tool has no output schema and no parameters, the description adequately explains the return value (templates with specific components) and provides examples of included models. It is complete for a simple retrieval tool, covering what the agent needs to know to use the templates.

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 input schema has zero parameters, so the description does not need to add parameter information. With no parameters, a baseline score of 4 is appropriate. The description covers the tool's purpose without needing parameter details.

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 it 'Get complete working examples for model fitting with the AxModelFitter.' It lists specific components of the templates (JAX function syntax, pint units, parameter bounds, file-based examples). This distinguishes it from sibling tools like fit_model, cross_validate_model, etc., which perform fitting or evaluation rather than providing examples.

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 explicitly advises to 'Use these as starting points - copy the structure and modify for your specific model.' This indicates when to use the tool. However, it does not provide explicit guidance on when not to use it or alternatives, though the sibling list offers context.

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