scf_list_functions

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

Annotations already provide readOnlyHint=true, and the description adds that it's a read operation any member can perform, plus the notable behavioral fact that the function set is identical for every tenant. It also discloses a dependency (needed for scf_create_team). This adds value beyond the annotation without contradiction.

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?

Two concise sentences with zero waste. The read hint and purpose are front-loaded, and the dependency on scf_create_team is a valuable addition. Perfectly structured for quick agent comprehension.

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 simple list tool with one optional parameter and no output schema, the description is complete. It explains the resource, the read-only nature, the cross-tenant consistency, and its role in team creation, covering all an agent needs to call it correctly.

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 100% for the single include_inactive parameter, so the schema already documents it fully. The description does not mention the parameter, but since the schema covers it, baseline 3 is appropriate; no additional meaning is needed.

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?

Clearly states it lists the platform's business functions, a specific resource, and distinguishes from siblings by noting it's the fixed set every team aligns to, identical for every tenant. Also connects to its use in scf_create_team, making its purpose unambiguous.

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?

Explicitly states it's a read operation available to any member and that it's needed for the function_id on scf_create_team, giving clear context for when to use it. It doesn't explicitly list alternatives or when-not conditions, but the purpose is so specific that it stands out among sibling list tools.

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