cubemx_load

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

Even though no annotations are provided, the description explicitly states 'read-only, does not modify any files' and discloses a path restriction (must be in allowed directory). It does not describe error handling or return format, but the output schema exists, so that is acceptable.

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 extremely concise: one sentence for purpose and one bullet for the parameter. Every piece of text adds value and no redundant information is present.

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 a simple single-parameter tool with an output schema, the description covers the essential aspects: what it does, the parameter semantics, and the safety/restriction. Nothing critical is missing.

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 only a string parameter named 'ioc' with no description. The tool description fills this gap by explaining that it is an absolute path to the .ioc file and must be within an allowed directory, adding meaningful context.

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?

Description clearly states the tool loads a .ioc project and reads back key configurations, with an explicit read-only note. This distinguishes it from siblings like cubemx_configure (which modifies) or cubemx_generate (which generates code).

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 provides clear context: this is a read-only inspection tool. It does not explicitly name alternatives or state when not to use it, but the read-only framing and the sibling tool names imply the intended use case.

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