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

The description goes beyond the annotations by explaining the one-way freeze, the ErrApplicationFrozen error on subsequent writes, and the rationale (what was submitted is what was reviewed). It also notes the destructive/non-idempotent nature, which aligns with the destructiveHint annotation. No contradiction.

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 dense but not bloated; it front-loads the core action and then explains the freeze behavior and error semantics. Every sentence adds meaningful context, though the phrasing is slightly convoluted in places.

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?

The description covers the key behavioral context: what happens on submit, why it's destructive, and what error to expect. With an output schema present and a single well-documented parameter, the description is sufficiently complete for an agent to invoke the tool correctly.

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 coverage is 100% and the single parameter (applicationId) is documented as a UUID value wrapper. The description doesn't add parameter-specific detail, but with full schema coverage and one obvious parameter, the baseline of 3 is appropriate.

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 (submitting/freezing an application) and the resource (the banking application), and it distinguishes the tool from ordinary field writes by explaining the freeze semantics. It doesn't explicitly name a sibling alternative, but the context makes the operation's purpose clear.

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 implies when to use this tool: when an application is complete and ready to be submitted, and it warns that subsequent writes will be refused. It doesn't explicitly name alternatives or exclusions, but the freeze behavior provides clear usage context.

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