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

No annotations exist, so the description carries the full burden and it mostly does not: it never says what the tool produces, whether it reads or writes anything, or what permissions it needs. Only "no setup, works in any LLM chatbot" conveys any behavior at all, and that is a portability claim rather than a disclosure of runtime behavior.

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?

Opening with the marketing line "Save hours every week" wastes the front-loaded position that should carry the core purpose. Three sentences are spent without a single concrete statement of function.

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?

With no annotations, no output schema, and no useful description, an agent has nothing to reason from except the tool name. Given the dense sibling neighborhood, a minimal explanation of what the summary contains and when it beats contract-check-tool was essential.

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 single optional "query" parameter has a 100% schema description, so the schema already explains it; the description adds no scope semantics, examples, or format hints beyond it. Baseline 3 applies where the schema does the heavy lifting and the description neither helps nor harms.

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?

"This contract summary tool toolkit" largely restates the name, and the one substantive clause describes something else entirely — "a battle-tested prompt and operating playbook for restaurant/brand growth." An agent cannot tell whether this summarizes contracts, produces F&B growth prompts, or is a chatbot instruction pack, and nothing distinguishes it from the contract-* 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?

There is no when-to-use, when-not-to-use, or alternative guidance of any kind. With nine sibling contract tools (contract-audit-tool, contract-check-tool, contract-sort-tool, etc.), the absence of routing guidance makes correct selection essentially impossible.

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