Snowflake Describe Masking Policy

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows this is a safe read against a live account. The description adds only the return contents, which the output schema already covers, and says nothing about permissions needed or how unqualified names resolve.

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?

A single front-loaded sentence that states the action and its outputs with zero filler. Nothing to trim and nothing buried.

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?

For a read-only describe tool with an output schema and a simple qualified-name parameter set, the description is just adequate. It omits how the optional database/schema qualifiers default when policy_name is unqualified, which is a real ambiguity given the sibling context tools.

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 description coverage is 0%, so the description carries the full burden for the three parameters, yet it mentions none of them. It does not explain that database and schema_name are optional qualifiers defaulting to the current context, which is the one piece of semantics an agent actually needs.

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 names a specific verb (describe) and resource (masking policy) and even enumerates what is returned: signature, return type, and body. That distinguishes it from snowflake_list_masking_policies, but it never explicitly routes the agent away from that sibling, so it stops short of the top band.

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?

There is no statement of when to use this tool versus snowflake_list_masking_policies or snowflake_describe_row_access_policy, and no prerequisites (e.g., required privileges) are mentioned. Usage is only implied by the word 'describe.'

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