Get one property

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the non-obvious fact that the two property spellings are separate properties holding separate data, which is useful. It does not describe return format or error behavior, but the output schema covers return values.

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?

Two sentences with no filler. The core operation is front-loaded, followed by the use case and the key caveat. Every sentence contributes essential information.

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 single-parameter, read-only tool with a complete input schema and an output schema, the description is sufficiently complete. It conveys the key caveat about property spellings and the permission-level return. A minor gap is the absence of alternative tool names, but the low complexity makes this a non-critical omission.

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 100% and already documents site_url, including the two spellings and the trailing-slash requirement. The description adds semantic value by explaining why the choice matters: the two spellings are separate properties holding separate data. This is meaning beyond 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?

States a specific verb and resource: 'Returns one property and the permission level this credential has on it.' The singular 'one property' clearly distinguishes it from list_sites, but it does not explicitly differentiate it from sibling get_verified_site, so sibling distinction is only partial.

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 concrete use case: 'Useful for settling which of the two spellings exists.' This gives clear contextual guidance on when to call this tool. It does not state exclusions or name alternative tools, so it stops short of full when-not guidance.

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