iaas_get_configuration_property

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds nothing beyond restating the HTTP verb and path — no note on what a configuration property contains, whether lookups can fail, or any permission requirement.

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 short lines with the action front-loaded and no filler. It is efficient, though arguably under-informative rather than genuinely concise for a description that has nothing else to offer.

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 two-parameter read tool with full schema coverage and no output schema, the definition is adequate but bare: it never explains what a configuration property is or what the response contains, which the absence of an output schema makes slightly more important.

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 description coverage is 100%, so the schema already documents both id and apiVersion. The description's URL template implies that id is a path parameter, adding only marginal value; the apiVersion format requirement is left entirely to the schema.

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?

States a specific verb+resource ('Get single configuration property') and the underlying REST path, which tells an agent it retrieves one entity by ID. It only implicitly distinguishes itself from the sibling iaas_get_configuration_properties (the plural list tool) through the word 'single'.

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 word 'single' hints that this is the by-ID fetch and the plural sibling handles listing, but there is no explicit when-to-use/when-not statement and no mention of alternatives, prerequisites, or error behavior for a missing ID.

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