Get permission by scope value or GUID

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

With no annotations, the description carries full burden. It discloses that searches cover Application and/or Delegated datasets and that a scope can exist in both, returning matches from each. However, it does not clarify behavior if both value and id are provided or if neither is provided, leaving some ambiguity. No annotation contradiction.

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 description is concise at three sentences, front-loads the core action, and contains no unnecessary words. Every sentence adds value.

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 tool with 3 parameters, no annotations, and no output schema, the description covers most key aspects: purpose, parameter usage, and dual dataset behavior. It is missing details on output format and handling of edge cases like providing both or neither parameter, but overall it is fairly complete.

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 coverage is 100%, establishing a baseline of 3. The description adds meaning by explaining the dual dataset behavior and the purpose of the 'kind' parameter, which goes beyond the schema's description. It also reinforces the 'either value or id' requirement.

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?

The description clearly states the tool does an exact lookup of a Graph permission by scope value or GUID. It distinguishes from sibling search tools by emphasizing 'exact lookup' and specifying the use of either value or id.

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 description implies when to use the tool (for exact lookup when the value or GUID is known) but does not explicitly mention when not to use it or contrast it with sibling search tools. Some guidance is provided by stating 'Provide either value or id', but more direct comparison would improve clarity.

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