get_environment_summary

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the 'high-level snapshot' and 'accessible' scoping, but it does not disclose output details, pagination, or any other behavior beyond what the annotations imply.

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 focused sentence with no filler. It front-loads the key verb and resource and communicates the read-only nature immediately.

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 zero-parameter, read-only, idempotent tool, the description is reasonably complete: it states what the tool produces (a high-level snapshot) and its scope (accessible Azure environment). The lack of an output schema is mitigated by the word 'snapshot' and the tool name, though the exact contents of the summary remain unspecified.

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 tool has zero parameters, so there are no parameter semantics to document. The description appropriately avoids inventing parameter-related details; with no parameters, a baseline of 4 is warranted.

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 identifies the operation as 'Get a read-only high-level snapshot' with a clear resource: 'the accessible Azure environment.' It is specific enough to distinguish from granular list tools, though it does not explicitly name a sibling or contrast itself with them.

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 phrase 'high-level snapshot' implies this tool is for a broad environment overview rather than deep investigation, but there is no explicit guidance on when to choose it over alternatives such as get_identity_access_summary or list_resources.

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