cbs_observations

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so read-only behavior is covered. Description adds no additional behavioral context (e.g., pagination, rate limits, data volume warnings). Minimal added value beyond 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?

Extremely concise: one sentence and a phrase. No redundant words. However, brevity compromises informativeness; a bit more structure would be beneficial.

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?

Complex tool with 9 parameters, no output schema, and nested objects. Description omits crucial context: how to obtain tableId, pagination behavior, output format defaults, and limitations. Lacks completeness for effective agent invocation.

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 0%, so description must compensate. Only mentions 'column selection' and 'dimension filtering' (implying select and filters parameters). Fails to explain other 7 parameters (top, limit, offset, dryRun, verbose, outputFormat, tableId). Insufficient for 9-parameter tool.

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?

Clearly states verb 'Fetch' and resource 'observations (data rows) from a CBS statistical table'. Distinct from siblings like cbs_table_info (metadata) and cbs_tables_search (table discovery). Specific verb+resource with implied scope.

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?

Implies use when needing data rows from CBS tables, but no explicit guidance on when to use alternatives or when not to use. Context is clear but lacks exclusion criteria.

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