md_scientific_gate_audit

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

With no annotations provided, the description carries the full burden. It discloses the notable behavior of not running an engine, which is useful. However, it does not mention whether the audit is read-only, requires specific permissions, or produces side effects, leaving behavioral transparency incomplete.

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 (12 words) that front-loads the core action 'Audit' and the key constraint 'without running any engine.' No filler or redundancy.

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?

Despite having an output schema, the tool has 5 parameters, including a confirmation_token and nested objects, with no annotations. The description is too sparse to provide adequate context for such a complex tool; it does not address the confirmation flow, prerequisites, or what 'frozen' means in practice.

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 adds no parameter information. None of the five parameters (e.g., confirmation_token, evidence_manifest, dry_run) are explained, so the description fails to compensate for the lack of schema descriptions.

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 states a specific action ('Audit') on a specific resource ('frozen target-model science contract') and adds a distinguishing mode ('without running any engine'). This sets it apart from sibling audit/readiness tools like md_architecture_compliance_audit or md_model_readiness_assess.

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 versus alternatives, nor are any exclusions or prerequisites mentioned. The phrase 'without running any engine' implies a use case but does not explicitly state it.

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