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

Annotations already declare a non-destructive, non-open-world write, and the description adds two real behavioral facts: the new project starts empty and is private by default, and it requires account-level create permission. It says nothing about duplicate-title behavior, quotas, or what identifier comes back, so the added context is useful but thin for a creation tool.

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?

A single front-loaded sentence with the action first and the definitional parenthetical after it; nothing is redundant. It is dense but every clause (empty, private, permission-gated) carries information an agent needs.

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 output schema, no parameter descriptions, and no annotations explaining the response, the description should say what a successful call yields (project id/handle) and what happens if basemap IDs are omitted. Neither is covered, leaving gaps an agent would hit on its first invocation.

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% across four parameters, so the description must carry the load — but it only obliquely covers ownerHandle ('under an account') and never mentions title, basemapIdDark, or basemapIdLight. The two basemap UUID parameters and any default behavior when they are omitted are entirely undocumented.

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?

States a specific verb and resource ('Create an empty private project') and immediately defines what a project is — a geospatial workspace holding map layers, datasets, styles, and analysis results. The scoping words 'empty' and 'private' separate this from the many project_* siblings that mutate an existing project, so an agent can identify it without opening the schema.

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?

Gives a clear precondition — the caller must have create rights on the target account ('under an account where the caller can create') — which tells the agent when the call is valid. It stops short of naming exclusions or pointing at an alternative when the account lacks permission (e.g., a request/approval flow), so it falls just short of explicit when/when-not guidance.

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