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

The description is otherwise rich—backend-side tier resolution, no MCP routing decision, auth requirements, error code -32001, idempotent no-op on SUBMITTED state—but it directly contradicts the annotation idempotentHint=false by claiming 'Idempotent: re-submit on SUBMITTED state is a no-op.' Per the rubric, a contradiction with annotations forces a score of 1.

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 front-loaded with the core action, then adds routing behavior, return contents, idempotency, and auth/error details in a labeled AUTH section. Every sentence adds operational value and the structure makes the long context easy to scan.

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 mutation tool with no output schema and zero parameter coverage, the description covers a great deal: routing authority, auth model, specific JSON-RPC error, idempotency semantics, and partial return shape. The main gaps are exact parameter semantics and the full response structure, but the operational context is unusually complete.

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%, so the description must compensate, but it never explicitly defines applicationId or agentBearer. It hints at a merchant-or-operator JWT and an application cohort, but does not map those concepts to the two required parameters, leaving the agent to infer the parameter meanings.

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 opens with a specific verb and resource: 'Trigger a Tier-1 / Tier-2 / Tier-3 lending application submission via the droplinked backend's TierRoutingService.' This clearly distinguishes the tool from the many read/verify/quote siblings and states exactly what operation it performs.

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 intended use is clear: call this when a lending application submission needs to be triggered. The auth note also clarifies that this is not a public read operation, and the final sentence explicitly contrasts it with credential-free discovery/catalogue/trust-fabric reads. It does not name specific sibling alternatives, but the context is strong enough to route an agent.

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