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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by stating exactly what the tool returns (Vee3-managed domains plus sites added via add_site), explaining the effect on later calls, and noting the token cost. It stops short of explicitly declaring read-only behavior or naming any permissions/rate limits, but for a simple list operation this is a minor gap.

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 compact and well organized: the primary purpose is front-loaded, followed by usage guidance, a fallback path, and cost. Every sentence serves a distinct purpose with no filler or repetition.

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 no-parameter list tool with an output schema present, the description is complete. It explains what the response contains, how to use the response to drive later calls, what to do if the list is empty, and even the token cost. There are no missing elements needed for correct 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?

The tool has zero parameters, so the schema already covers everything. The description adds value by explaining how the returned site_url values are used in subsequent calls, which is useful context beyond the empty input schema. This matches the baseline for a no-parameter tool.

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 opens with a specific verb and resource: 'List Search Console properties for this account.' It clearly distinguishes this listing tool from related tools like get_site or add_site by focusing on discovery of all properties, and references the exact workflow around site_url.

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?

The description explicitly says when to call this tool: 'Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response.' It also gives a concrete fallback when no properties appear: use add_site or domains.register. This leaves no ambiguity about when and how to use it.

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