ms_geology_apply_substitutions

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

With no annotations, the description must disclose behavior. It only hints at safety by mentioning 'nonproduction candidate' but omits side effects, permission requirements, irreversibility, or the roles of dry_run and confirmation_token.

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 concise sentence that front-loads the primary purpose. It is easy to parse, but the brevity comes at the cost of missing crucial 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 tool with 9 parameters, 6 required, and no annotations, a one-sentence description is inadequate. It lacks practical context about workflows, dry-run semantics, idempotency, or confirmation steps, making it insufficient for reliable agent use.

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?

Schema description coverage is 0%, and the description does not explain any parameters. Terms like 'substitutions', 'confirmation_token', and 'idempotency_key' remain undefined, so the description adds negligible value to the schema.

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 identifies the action (Apply), the resource (P1 substitution ledger), and the result (return a nonproduction candidate). It distinguishes itself from sibling tools like ms_geology_apply_hydroxylation_ledger by specifying P1 substitutions.

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?

No guidance is provided on when to use this tool or which alternatives might be more appropriate. The description does not mention contexts, prerequisites, or exclusion scenarios.

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