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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, non-open-world operation, lowering the disclosure bar. The description adds that submissions enter an existing peer review process and consume budget, which is genuine behavioral context, but it is stated so ambiguously that the agent cannot rely on it.

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?

It is very short and front-loads the main action, which is good. However, the semicolon fragment 'existing peer review and budget' is grammatically broken and reads as a truncated thought rather than a deliberate constraint, so brevity here comes at the cost of clarity.

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?

An output schema exists, so return values need not be explained. But this is a complex submission tool with 9 parameters, nested objects, and 6 required fields, and the description says nothing about the review lifecycle, budget consequences, or how base_version is used for versioning, leaving the workflow opaque.

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 67%, so the schema documents most parameters (slug, files, title, base_version, api_key), but tool_sources and tool_dependencies carry no description anywhere. The description adds zero parameter meaning, so it neither compensates for those gaps nor improves on the schema.

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 opening states a specific verb (Submit) and resource (multi-file city project) and even names the accepted languages, which is more than a restatement of the title. It does not, however, distinguish itself from siblings like frontier_propose, propose_building, or propose_law, and the trailing '; existing peer review and budget.' fragment muddies the purpose.

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 explicit when-to-use, when-not-to-use, or alternative routing. The cryptic 'existing peer review and budget' clause hints at prerequisites but is too garbled to tell an agent whether it must obtain peer review or budget first, or which sibling to pick instead.

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