creo_start_resident_and_get_basic_model

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

The annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context: it starts or reuses a resident bridge, is bound to the current Creo session, exits automatically when Creo closes, and avoids traversal work. These are meaningful behavioral details beyond the structured hints.

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 dense sentence that front-loads the critical directive ('first command in every new session') and then states scope, exclusions, and lifecycle in order of importance. Every clause adds necessary information with no filler.

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 zero-parameter handshake tool with no output schema, the description is complete: it explains when to call it, what it returns, what it avoids, and how the bridge lifecycle works. An agent has enough context to invoke it correctly in a new session.

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 there are no parameter semantics to document; this is the baseline-4 case. The description reinforces that no user input is needed beyond calling the tool.

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 names a specific action (start or reuse the resident bridge) and resource (current Creo session), and precisely lists the data it retrieves: working directory, current model name, type, and outer dimensions. It clearly distinguishes itself from siblings by stating it is the first command in a new session and that it does not traverse features, dimensions, parameters, or assembly components.

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 says this should be the first command in every new Creo session, which is strong when-to-use guidance. It also states what the tool deliberately does not do, providing clear when-not guidance relative to other inspection tools like creo_get_features or creo_get_dimensions.

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