Mce Summary

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

No annotations are provided, so the description must carry the full behavioral burden. It says nothing about what the summary contains, whether it is read-only, what side effects if any it has, or what its output looks like. 'Legacy' is the only behavioral hint, and it is too weak to act on.

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?

It is extremely short at four words. Brevity is not a flaw by itself, but here the brevity comes at the cost of meaning; the sentence is front-loaded with a vague modifier rather than useful information.

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 summary tool with no annotations and no output schema, the description should explain what is summarized and how the result is delivered. It does none of that, leaving the agent unable to predict whether the call is safe, useful, or what it returns.

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 the baseline is 4. The description adds nothing on parameters, but there is nothing to add.

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 'Legacy compact MCE summary' is essentially a restatement of the title 'Mce Summary' with the added but vague qualifiers 'Legacy' and 'compact'. It does not state a specific verb or resource with enough precision to distinguish it from siblings like zemax_mce_add_operand or zemax_nsc_summary.

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 indication of when to use this tool, when not to use it, or what alternatives exist. The word 'Legacy' hints at deprecation but the description draws no actionable distinction from other MCE or summary tools.

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