list_assets

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

With no annotations present, the description carries the full behavioral burden and discloses almost nothing: no read-only confirmation, no permission requirements, no pagination or result-size behavior. "Returns: List of assets with details" is the only behavioral statement, and an output schema already covers return shape.

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?

Front-loaded with the core action in the first sentence, with parameter and return details in compact labeled blocks. The Returns section is largely redundant given an output schema exists, costing a little space.

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 single-optional-parameter list tool with an output schema available, the description covers the action, the filter, and its valid values. Remaining unknowns (pagination, permissions) are secondary for a read-only enumeration.

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 0% and the schema's anyOf string/null gives no constraint, so the description's enumeration of PHYSICAL, VIRTUAL, CLOUD, DATA, PERSONNEL is genuinely load-bearing — it is the only source of the allowed values. It does not state that the parameter is optional, which the schema default partially implies.

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?

"List all assets in the asset inventory" gives a clear verb and resource, and the asset domain distinguishes it from siblings like list_controls, list_policies, and list_personnel. It stops short of naming a specific alternative to route against, but the resource is unambiguous.

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 description offers no when-to-use context, no prerequisites, and no mention of sibling tools such as list_personnel or list_devices that also enumerate inventory-like entities. An agent must infer applicability purely from the tool name.

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