get_analytical_model

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

With no annotations, the description carries the full burden. It clearly states it returns the OData service document, entity sets, dimensions, measures, and query capabilities, and explains how CSDL metadata is parsed. However, it does not mention error handling, authorization needs, or rate limits.

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 sentences, efficiently front-loaded. First sentence states the primary action and return types, second adds detail on metadata parsing. No redundant information.

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?

Despite no output schema, the description conveys the main components returned (entity sets, dimensions, measures, query capabilities) and the parsing logic. It lacks details on response structure or error cases, but is sufficient for most use cases given the tool's straightforward nature.

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 three parameters. The description adds value by explaining that 'include_metadata' controls the inclusion of parsed CSDL metadata, and implicitly links 'asset_id' to the analytical model. It surpasses the baseline by providing context beyond the schema definitions.

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 uses a specific verb ('Get') and identifies the resource ('analytical model') clearly. It distinguishes from siblings like 'get_analytical_metadata' by specifying it returns the OData service document and parsed CSDL metadata with dimensions/measures.

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 implies usage for retrieving full metadata of a specific model but does not explicitly state when to use over alternatives like 'get_analytical_metadata' or 'list_analytical_datasets'. No when-not-to-use guidance is provided.

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