creo_get_current_model

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

The annotations already convey read-only, idempotent, and non-destructive behavior. The description adds value beyond annotations by explicitly promising that the tool will not modify, save, or display the model, which clarifies an additional behavioral guarantee not present in the structured metadata.

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, well-structured Chinese sentence that front-loads the action and resource, then appends the key behavioral restrictions. There is no wasted text.

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 parameter-less, read-only introspection tool, the description covers the important safety aspects and the target of the read. It is slightly vague about what 'model info' specifically includes, and there is no output schema, but the overall context is sufficient for basic selection and invocation.

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 tool has zero parameters, so schema description coverage is trivially 100% and there is no parameter semantics to explain. A baseline of 4 is appropriate because there is no missing parameter information to compensate for.

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 the tool reads the currently running Creo session and the current model information, which is a specific verb and resource. It does not explicitly differentiate itself from sibling read tools like creo_get_dimensions or creo_get_features, so it misses the highest bar for sibling distinction.

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 implies a safe read-only use case by explicitly stating it will not modify, save, or display the model. However, it does not name alternatives or provide any when-to-use versus when-not-to-use guidance relative to the many sibling tools.

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