get_resource

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

No annotations provided, so description carries full burden. It explains truncation behavior and return value, but does not explicitly state that the operation is read-only. However, the action word 'Retrieve' implies no side effects, and the description is otherwise transparent about parameters and results.

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?

Description is concise with structured Args/Returns sections. Each sentence serves a purpose. Could be slightly tighter by removing default mention in description since schema already has default, but overall good.

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?

Given output schema exists and sibling tools context, the description covers usage, parameters, and return value adequately. Missing explicit mention of permissions or rate limits, but these are not critical for a retrieval tool. High completeness for the 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 covers both parameters with descriptions (100% coverage). Description adds context about truncate_length default and setting to None for full descriptions, but this is complementary rather than essential beyond what schema provides. Baseline 3 is appropriate.

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 'Retrieve a specific resource by its ID' and specifies it is for catalog resources like table, column, view. This distinguishes it from sibling tools like list_resources (listing) and search_data_assets (searching).

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 'Use this to get full details ... after finding it through list_resources or search_data_assets,' providing clear when-to-use and implicitly when-not-to-use (e.g., not for listing or searching).

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