list_graph_critical_application_permissions

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

Annotations already establish readOnlyHint and idempotentHint, so the safety profile is covered. The description adds the scoping detail of filtering to critical Graph Application Permissions, but it does not define what makes a permission 'critical' or disclose sorting/pagination/output behavior. It does not contradict annotations.

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 a single concise sentence with no filler. It front-loads the action and the resource, which is appropriate for a simple list tool.

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 simple read-only list with one optional parameter, this is close to sufficient. However, the description omits details about the meaning of 'critical' and the output contract, and there is no output schema to fill that gap. A slightly richer description would improve completeness.

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?

The single parameter 'limit' is not mentioned in the description, and schema_description_coverage is 0%. However, the parameter is simple and self-espianatory given the schema's type and default. The description does not add meaning, but the gap is minor for this optional integer.

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 states a specific action ('Lista') and resource ('aplicações/service principals') filtered by 'Microsoft Graph Application Permissions críticas'. It is clear and can be distinguished from broad permission tools, but it does not explicitly contrast with siblings like graph_permissions or list_application_provenance.

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 alternatives, no prerequisites, and no exclusions. The only signal is the name, which is insufficient for an agent deciding between this and the many permission-related sibling tools.

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