data_profile

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

No annotations, but description fully discloses what the tool returns (column stats, sample values) and implies read-only analysis. Minor omission: no mention of idempotency or caching.

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?

Four concise sentences, front-loaded with the most important usage context. No wasted words; each sentence adds essential info.

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?

Output schema exists, so description doesn't need to detail return format, but it still lists return content. Tool is well-defined with no missing aspects for an agent to use correctly.

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%, but description adds context: 'Row dicts from get_resource_data()' for data param and clarifies sample_size as sample values per column. Also explains return data types.

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 verb ('Understand') and resource ('data structure'), specifies it's for before charting/transforming, and distinguishes from siblings by listing exact output (column names, types, etc.).

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?

Explicitly says 'ALWAYS use after get_resource_data() and before create_chart()', providing clear sequential context and when-to-use guidance.

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