security-get-role

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description does add one real behavioral fact not explicit in the schema: identity and filter are mutually exclusive ('exactly one'). It still omits return shape and result-size behavior (the 'full' flag's 100,000+ char caveat lives only in the schema).

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, both earning their place: purpose/scope first, invocation constraint second. No filler, no restatement of the name, front-loaded.

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?

No output schema exists, and for a low-complexity read tool with fully documented params and readOnlyHint coverage, the description supplies what an agent needs to select and invoke it. Only a brief note on what is returned (a list of roles) is missing.

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 the baseline is 3. The description reinforces the exact-vs-wildcard distinction and the mutual-exclusivity rule already implied by the schema ('Supply this or identity'), adding marginal but not new meaning.

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 Sitecore roles') and clarifies the two lookup modes (exact identity vs wildcard filter), which separates it from siblings like security-get-role-member. Clear and specific, though it never names an alternative tool to route against.

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 an operational invocation rule ('Supply exactly one of identity or filter') but says nothing about when this tool is preferred over related siblings such as security-get-role-member or security-get-domain. Usage is implied by the constraint rather than framed as guidance.

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