get_gate2_readiness_check

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 rule-based nature, the possible result values (pass/warn/fail/not_applicable), the inclusion of reference URLs, and the explicit limitation that it is not a prediction of Gate 2 outcome. This is strong behavioral disclosure beyond simple read/write status.

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?

Three concise sentences with no padding. The first sentence immediately identifies the tool's purpose, and each subsequent sentence adds essential value (evaluation method, output format, caveat).

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?

Given the lack of an output schema, the description adequately explains what the tool returns (per-rule pass/warn/fail/not_applicable with reference URLs). It covers the main behavioral and output aspects, though it could theoretically mention how to interpret a final outcome, but the 'not a prediction' caveat covers the key interpretive risk.

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 100%, so the schema already documents all 9 parameters thoroughly. The description adds no additional parameter-level detail beyond referring to 'project inputs', which is adequate but does not go beyond 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 states the tool performs a rules-based Gate 2 readiness checklist, evaluating project inputs against NESO entry criteria and returning per-rule results. This is a specific verb+resource that distinguishes it from sibling data-retrieval tools.

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: it is for project inputs and assesses Gate 2 readiness. It does not explicitly state when to use it over alternatives, but no sibling tool performs this function, so the usage context is sufficiently clear.

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