Check Delete Eligibility

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

No annotations provided, so description carries full burden. It effectively discloses return semantics: 'whether deletion is allowed' and specifically 'lists blocking dependencies,' explaining what 'eligibility' means. Missing explicit read-only/side-effect disclosure, though 'Check' implies safety.

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 tightly constructed sentences with zero waste. First sentence establishes purpose, second discloses return value. Front-loaded with key action and appropriately brief given rich schema and output schema availability.

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?

Sufficient for a 3-parameter inspection tool with 100% schema coverage and existing output schema. Description provides high-level return value summary without duplicating output schema details. Could mention environment default behavior, but omission acceptable.

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 has 100% description coverage with detailed componentType examples. Description adds no parameter-specific guidance beyond schema, which is acceptable given comprehensive schema documentation. Baseline 3 appropriate.

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?

Description uses specific verb 'Check' with clear resource 'PowerPlatform component' and distinct context 'safely deleted.' It differentiates from sibling check-component-dependencies by focusing specifically on deletion safety and blocking dependencies rather than general dependency listing.

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 implied usage context (use when considering deletion), but lacks explicit guidance on when to use this versus check-component-dependencies or other inspection tools. No 'when not to use' or prerequisite guidance provided.

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