revoke_or_disable_app_registration

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

With no annotations, the description carries the full burden. It discloses that the tool only generates dry-run commands rather than executing them, which is key. However, it fails to mention other behaviors like authentication requirements, error handling, or output format.

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. It front-loads the key concept (dry-run generation) without extraneous detail, making it easy to read. However, it could benefit from brief bullet points for clarity.

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?

Given the tool has 3 parameters, an enum, and no annotations, the description is too sparse. It omits the output format, error scenarios, and prerequisites. The existing output schema is not referenced, so the agent lacks complete context.

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 0%, so description must add meaning. It mentions 'disable sign-in or revoke credentials' which maps to some action enum values but not all. It does not explain the app_id or key_id parameters, leaving their semantics unclear.

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 it generates dry-run commands for disabling sign-in or revoking credentials, but the action enum includes additional actions like remove_permission and rotations, which are not mentioned. It identifies the verb 'generates' and the resource 'app registration commands', but misses full scope.

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?

No guidance on when to use this tool versus siblings like audit_app_registrations or generate_remediation_plan. The description implies it's for generating remediation commands, but without explicit context, the agent may misuse it.

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