domain_get_property

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. Beyond that, the description adds nothing about authentication requirements for api_key, rate limits, error behavior for an invalid listing_id, or what 'details' actually contains.

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 definition is a single front-loaded sentence with no wasted words. It is appropriately sized but so terse that it omits useful context, which is a completeness issue rather than a conciseness problem.

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?

There is no output schema, both parameters lack schema descriptions, and the description does not explain what fields are returned or where listing_id should come from. For a simple lookup this is nearly complete, but the undocumented api_key and return-content gap leave it inadequate.

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%, so the description must carry the burden. It only implies that listing_id identifies the property, and it says nothing at all about the api_key parameter or accepted identifier format, leaving both parameters semantically thin.

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 (get details for a Domain property listing), so the agent can tell it is a detail lookup rather than a list/search. It does not explicitly differentiate itself from the sibling domain_search_listings, which keeps it at 4 rather than 5.

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 phrase 'specific Domain property listing' implies this is used after a listing_id is known, likely from domain_search_listings, but no alternative is named and no explicit when-to-use guidance is given. Usage is inferable but not stated.

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