catalog_get_adhoc_analysis

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

No annotations provided, so description carries full burden. It discloses that profile_ready and information_privacy are reported only when the job carries a resource, explains the time gap between job completion and profile readiness, and describes polling behavior.

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?

The description is detailed but front-loaded with purpose, then explains nuance. Every sentence adds value, but could be slightly more concise without losing clarity.

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 one required parameter and presence of an output schema, the description fully explains the polling workflow, output fields (profile_ready, information_privacy), and the edge case when the job carries a resource. No gaps.

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?

Only one parameter (job_id) with 100% schema coverage. The description does not add new semantic information beyond the schema's 'The analysis job id returned by catalog_run_adhoc_analysis.' Baseline 3 applies.

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 the tool gets the status of an ad-hoc analysis job and whether its profile is ready. It specifies the verb 'get status' and resource 'ad-hoc analysis job', and distinguishes from a simple job status by explaining the profile readiness gap.

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?

Explicit guidance: 'Poll until profile_ready is true, then download.' Explains why job completion status is insufficient and provides the condition for safe download. References the same gate as catalog_download_table_profile, hinting at an alternative tool.

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