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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds a real behavioral trade-off beyond that: the default resolves member properties while embeds="" skips that resolution for a faster, names-only listing. It doesn't mention pagination or result limits, which keeps it from a 5.

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?

Three short sentences, each earning its place: identity/location first, sibling disambiguation second, performance option last. No filler and nothing buried.

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 an output schema present, return-value explanation is correctly omitted. For a single-optional-parameter read tool, the description covers what it lists, how it differs from the nearest sibling, and the one meaningful parameter behavior. Only the full set of valid 'embeds' values is left unstated.

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% and the single 'embeds' parameter has no description, so the description must carry the meaning — and it does, explaining that embeds="" skips member resolution and implying the default populates members. It doesn't enumerate other accepted values or confirm the exact default string, leaving a small gap.

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 ('List the Property Groups saved inside Rent Manager'), gives the UI location for grounding, and explicitly distinguishes the result set from the sibling tool list_portfolios. An agent can pick this over list_portfolios without opening either schema.

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?

Explicitly states when this tool is the right choice versus the alternative ('distinct from the dash-prefix portfolios returned by list_portfolios'), and gives a concrete condition for the faster path (embeds="" for names-only). It stops short of stating when NOT to use the tool or any prerequisite/connection requirements.

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