sac_export_get_dimension_master

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

No annotations provided, so description carries full burden. It only states the tool gets data, but fails to disclose any behavioral traits like pagination (though parameters imply it), authorization needs, rate limits, or side effects. Minimal transparency for a data retrieval tool.

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?

Extremely concise single sentence, front-loading the verb and resource. However, it omits important context that would normally be provided in a slightly longer description. Still, brevity is a strength given the schema covers param details.

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?

With no output schema, the description should explain the response structure (e.g., entity set format, fields). It doesn't. Also, no guidance on parameter combinations or usage patterns. The tool has 9 parameters but the description offers no integrative context.

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 each parameter having a description. The tool description adds no additional semantic value beyond the schema; it merely restates the purpose. Baseline 3 is appropriate since schema already documents parameters well.

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?

Description clearly states it gets master data for a single dimension, referencing the entity set naming pattern. However, it doesn't explicitly differentiate from similar siblings like sac_export_get_master_data or sac_export_get_dimension_master_hierarchy, which could cause confusion when multiple tools target master data.

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?

No guidance on when to use this tool versus alternatives (e.g., sac_export_get_master_data for all dimensions). The description implies single-dimension use but doesn't state prerequisites or context. With many sibling tools, this omission hinders correct selection.

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