List properties

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

The annotations already convey read-only, idempotent, non-destructive behavior, and the description adds meaningful context beyond them: permissionLevel meanings, the unverified-property state, and that data calls for unverified properties return 403. This helps the agent understand real-world behavior without contradicting annotations.

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?

Every sentence earns its place: the first sets scope and output, the second gives a diagnostic trigger, and the third defines permission levels. The most important usage guidance is front-loaded, and there is no filler or repetition of schema details.

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 parameters, no required input, and an output schema already present, the description fully covers what an agent needs to call this tool correctly. It explains the output semantics, edge cases, and the recommended diagnostic workflow, leaving no obvious gaps.

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 baseline for this dimension is 4. The description cannot add parameter-level semantics, but it enriches the meaning of the permissionLevel values that appear in the output, which is useful context.

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 states a specific verb and resource: lists every Search Console property the credential can see, with the permission level on each. It clearly differentiates from siblings like list_verified_sites by explicitly including unverified properties and by focusing on what the credential can access.

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?

Provides a strong, concrete trigger: the first call to make when anything returns 403. It also tells the agent how to interpret an empty list for fresh service accounts, but it does not explicitly name sibling alternatives or state when not to use this tool.

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