Describe one system or software row

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

Annotations already state read-only/idempotent/non-destructive. The description adds that this is a mirror of the same register as controlcenter_list_resources and points to that tool for the authority note, which is useful behavioral context beyond the 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 well-structured sentence that front-loads the core purpose and only adds the cross-reference to the list tool. No filler or redundancy.

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 simple single-resource lookup and annotations covering read-only behavior, the description is sufficiently complete: it conveys scope, input source, and a pointer to the authority note. There is no output schema, but 'full row detail' is an adequate expectation for this simple operation.

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 already covers id and type at 100% coverageهار, but the description adds that the numeric id comes from controlcenter_list_resources and that resources are systems or software, helping disambiguate what identifier to supply.

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?

Uses a specific verb ('describe') and resource ('one resource' / 'single system or installed software entry'), and ties the identifier to controlcenter_list_resources. This clearly distinguishes the tool from sibling describe tools like describe_mcp and describe_stack.

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?

Clearly signals that the tool is for fetching full row detail for one resource by its numeric inventory id from controlcenter_list_resources. It does not explicitly name alternative tools or exclusion cases, but the scope is unambiguous.

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