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

With no annotations, the description carries the full burden of disclosing behavior. It does not mention whether this creates a new record, triggers a workflow, requires authentication, has side effects, or returns a result. Agents are left entirely in the dark about what calling this tool actually does.

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 short but this is under-specification rather than conciseness. The two sentences do not earn their place because they offer no operational information, only a restatement of the name and a URL reference.

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 tool named submit_underwriting_case with no annotations, no output schema, and no parameter docs, the description is entirely inadequate. An agent cannot determine the purpose, data required, workflow placement, or result of this tool.

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?

The tool has zero defined parameters and the input schema only consists of a root object with additionalProperties: true. Since no parameter semantics need to be documented, the 0-params baseline of 4 applies; the description adds nothing but the schema imposes no parametric burden.

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 is a tautology: 'MCP-Agents tool submit_underwriting_case' merely restates the tool name, and 'Same name as the live catalog' adds no functional meaning. It fails to state what the tool does, what an underwriting case is, or what submitting entails, and it does not distinguish the tool from its siblings.

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 about when to use this tool versus alternatives such as submit_documents, run_credit_screen, or prepare_ic_memo_outline. There is no mention of prerequisites, sequencing, or exclusions, so an agent has no basis for selecting it.

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