submit_application

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

Annotations already declare openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by naming the consent/confirmation gate and warning that a successful submit is not a confirmed booking, which is a non-obvious outcome caveat that no structured field states.

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?

Two short sentences with zero padding, and the critical precondition is front-loaded before the outcome caveat. Every clause carries information an agent needs.

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 seven-parameter, nested-object write with no output schema, the definition is thin: it never says what a successful submit returns or what to do on an uncertain result (idempotency detail lives only in the requestKey schema description). The precondition and the booking caveat do cover the riskiest decisions, which keeps it at minimum viable rather than inadequate.

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 only 43% across seven required parameters, so the description must carry weight, and it does not. It never mentions estimateId, catalogVersion, documentVersion, or the nested contactProfile, and it adds nothing to consent/userConfirmed beyond restating them in prose.

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 gives a verb ("Submit") but the resource is only available from the tool name; it never says what an application is or what happens on success. The one clarification, "This does not confirm a booking," bounds the effect negatively rather than stating it, leaving the agent to infer the operation from the name and 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?

"Submit only after user confirmation and contact consent" is an explicit precondition that gates invocation, which is exactly what an agent needs to know before a write. It stops short of naming alternatives (e.g., edit_estimate vs save_estimate), so it gets 4 rather than 5.

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