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

No annotations are provided, so the description must carry the full behavioral burden, but it does not explain what the tool actually does with the optional query, what output it produces, or whether it is read-only or mutating. It adds only product-packaging details such as being a prompt kit with instructions and 30-day support, leaving core behavior undisclosed.

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 not front-loaded with the tool's function; the first sentence is an unrelated marketing tagline about restaurant and brand intelligence. The remaining sentences emphasize prompt-kit packaging and support rather than essential invocation details, so several sentences do not earn their place.

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 one-parameter tool with no annotations and no output schema, the description should clarify the tool's actual operation and deliverable. Instead it describes a commercial prompt kit and support promise, not what the tool computes, returns, or how the optional query affects behavior.

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 input schema has 100% description coverage for the single optional 'query' parameter, so the schema already explains its purpose. The description does not mention the parameter or add any semantics beyond the schema, which is acceptable given the high coverage baseline.

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 mostly restates the tool name as a 'reno contract guard workflow' and wraps it in marketing language about an 'AI-powered restaurant & brand intelligence pack.' It does not clearly state the concrete verb and resource, such as whether the tool audits, generates, or reviews renovation contracts, so an agent cannot confidently distinguish it from siblings like renovation-quote-guard or rent-contract-guard.

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 guidance on when to use this tool versus similar contract or renovation tools, nor any prerequisites, exclusions, or scenarios. The only usage-adjacent statements are 'no prompt engineering needed' and a support promise, which do not help an agent choose between alternatives.

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