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

Beyond the annotations it discloses real side effects: Seovyn reads the site, plans first keywords, and makes the new org the dashboard's current organization. 'Can't be undone from here: needs confirm' adds the irreversibility and approval-loop context that readOnlyHint=false alone does not convey, though it sits slightly awkwardly against destructiveHint=false.

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?

Dense but purposeful: mode one, mode two, side effects, then the confirm warning in that order. Sentence fragments cost some readability but no line is filler.

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 6-parameter creation tool with no output schema, the description covers the two input shapes, the downstream effects, the confirm gate, and the permanence warning. The remaining gap is an unclear name-versus-businessName distinction in the no-website branch.

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 only 33%, and the description compensates partially by grouping fields into the two creation modes. However, it never distinguishes 'name' from 'businessName' or says what 'description' should contain beyond implying it feeds site building, leaving the highest-risk fields under-specified.

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 conveys a specific resource (a new organization tied to a website) and lays out the two creation modes with their field shapes. The verb 'create' is only implied by 'A new organization', but an agent can still tell this apart from every sibling, none of which create orgs.

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?

It explicitly says which mode to use for which situation: {name, website} for an existing site versus {name, noWebsite, businessName, description} for a business without one. It also states the confirm requirement, so the preview-then-confirm sequence is clear; what is missing is any routing versus siblings.

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