get_asset_variables

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

With no annotations provided, the description fully discloses the tool returns variables (name, type, default, nullable, multi_value), filter annotations, and the column list. It implies a read-only operation and adds context beyond the name, though it could mention prerequisites like asset deployment status.

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 two sentences: first states core functionality, second adds usage guidance. It is relatively concise and well-structured, though the first sentence is slightly lengthy.

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 tool with 2 params, no output schema, and no annotations, the description provides a good overview of inputs and outputs. However, it lacks details on output structure (e.g., array of objects) and possible error conditions, leaving some gaps in completeness.

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 coverage is 100% with descriptions for both parameters. The description adds some context by explaining the asset type (view/analytic model), but does not significantly enhance the meaning beyond the schema. Baseline of 3 is appropriate given high coverage.

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 clearly states the tool retrieves input parameters/variables and filter-capability annotations from OData $metadata of a SAP Datasphere asset. It specifies the verb 'Retrieve' and the resource, and distinguishes from siblings by mentioning it is for parameterised assets like views or analytic models.

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 explicitly says when to use this tool: when the asset is parameterised and variables need to be known before querying. It provides clear context for use but does not mention when not to use it or suggest alternatives among the many sibling tools.

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