Get simulation settings

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds the useful scope detail that it returns the full settings snapshot (including mesh deck size and dump config) rather than a subset, which is behavioral context beyond annotations. It does not describe output structure, defaults, or how missing values are represented, so it adds value but not richly.

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?

Front-loaded with the payload contents in one dense sentence, then a short usage sentence. The trailing '[bulc-mcp rules] GEN-006, GEN-010, GEN-016' tag is minor noise for a read-only getter, keeping it just below top marks.

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?

With no output schema, the description partially compensates by enumerating the returned settings categories, which is exactly what an agent needs to know before deciding to call it. Annotations fully cover safety. Only the exact return format/nesting is unspecified, a minor gap for a zero-arg getter.

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 per the rules the baseline is 4. There is nothing for the description to disambiguate, and it correctly implies the tool is argument-free by framing it as a single read call.

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?

Specific verb (Read) plus a precise resource (every simulation setting) with an explicit enumeration of what is covered: time, SIMULATION_MODE, turbulence, numerics, ambient/MISC, dump intervals/Plot3D, mesh deck size. This lets an agent distinguish it from narrower siblings like get_numerics or list_raw_namelists without opening any schema.

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?

Explicitly states when to use it: 'Use it before changing settings so you know what is already explicit.' That is a clear context. It does not name alternative readers (get_numerics, get_config_summary, list_raw_namelists) or say when not to use it, so it stops short of the top tier.

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