blueprint_list_property_groups

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing beyond the endpoint path: no note on pagination defaults, large result sets, or how 'top'/'skip' interact with 'page'/'size'.

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?

It is very short and front-loaded, but the second line mostly restates the endpoint already present in the annotation title, so space is not used to add meaning. Efficient but under-informative.

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?

A 12-parameter listing tool with no output schema should at least describe result shape or pagination semantics. Given the schema richness (which prevents the score from being lower), the description is still noticeably thin and leaves behavior and usage context for a complex listing operation unexplained.

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%, so all 12 parameters are already documented in the schema; baseline 3 applies. The description adds no clarification about conflicting pagination or sort options, but that is not required when the schema is complete.

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?

'Lists Property Groups' states a specific verb and resource, clearly distinguishing a collection listing from sibling tools like blueprint_get_property_group, blueprint_create_property_group, and blueprint_delete_property_group. The GET path adds a little extra confirmation of read scope, but sibling differentiation is only implicit through the verb 'Lists'.

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?

There is no guidance on when to use this tool versus getting a single property group or how to use filtering for a narrowed result. The agent must infer usage entirely from the tool name.

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