scm_list_file_blocking_profiles

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

No annotations are provided, so the description carries the full burden. It describes the tool as a list operation, which implies read-only behavior, and adds context about what file blocking profiles do. However, it lacks details on behavioral traits like pagination, rate limits, authentication needs, or error handling.

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 appropriately sized with three sentences and a parameter section. It is front-loaded with the core purpose, followed by explanatory context and parameter details. No wasted sentences, though the parameter section could be integrated more smoothly.

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 no annotations, 0% schema coverage, and an output schema present, the description is fairly complete. It covers purpose, parameter meanings, and context about file blocking profiles. With an output schema, it need not explain return values, but could add more on usage or behavior.

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 must compensate. It explains both parameters: 'folder' as the folder name to scope the query, and 'tsg_id' as optional with a default. This adds meaningful semantics beyond the bare schema, though it could specify format or constraints for 'folder'.

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 specific action ('List file blocking profiles'), the resource ('in a folder'), and the purpose of file blocking profiles ('control which file types are allowed, blocked, or forwarded to WildFire for analysis'). It distinguishes from siblings like 'scm_get_file_blocking_profile' (singular get) and 'scm_create_file_blocking_profile' (create).

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 implies usage by specifying the folder parameter scopes the query, but it does not explicitly state when to use this tool versus alternatives like 'scm_get_file_blocking_profile' for a single profile or 'scm_search' for broader queries. No exclusions or prerequisites are mentioned.

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