Snowflake List Streamlits

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds only the resource scope and nothing about authentication, result limits, pagination, or filtering behavior, making this the minimum viable disclosure.

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 a single, front-loaded sentence with no filler. It is optimally concise for what it attempts to convey.

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?

Although an output schema covers return values and annotations cover safety, the definition is incomplete for a list tool with three undocumented optional filters. It should explain what the pattern, database, and schema_name parameters filter and what the default scope is.

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?

The tool has three optional parameters, pattern, database, and schema_name, with 0% schema description coverage. The description never mentions these parameters or explains their filtering semantics, so the agent receives no meaning beyond the bare parameter names.

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 gives a specific verb and resource: 'List Streamlit applications hosted in Snowflake.' That is clear and distinct from sibling tools named describe_streamlit, but it does not explicitly differentiate itself from the adjacent describe tool or other list siblings.

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 guidance on when to use this tool versus alternatives such as snowflake_describe_streamlit, nor any exclusions or preconditions. The listing purpose is only implied by the verb 'List'.

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