scf_get_engagement_scope

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

Beyond the readOnlyHint annotation, the description discloses important behavioral details: the scope is frozen, rows carry a catalog lifecycle badge, and controls deprecated since the freeze still render as marked. This gives the agent meaningful expectations about the data without contradicting the annotations.

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 focused sentence with no filler. It front-loads the core purpose, then adds the role constraint and the key behavioral nuance about deprecated controls in a compact, efficient way.

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 two-parameter read-only tool with fully documented parameters, the description is complete enough for an agent to select and invoke it correctly. It covers what the tool does, who can call it, and an important output behavior, so no critical missing context remains.

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 schema already covers both parameters fully, including format, required status, and provenance instructions ('obtain from scf_list_organizations' / 'scf_list_engagements'). The description adds no parameter-specific semantics, but none are needed given the high schema coverage.

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 uses a specific verb ('Get') and a precise resource ('an engagement's frozen control scope'), and clarifies that this is a read operation. The phrase 'frozen control scope' distinguishes it from related sibling tools like scf_list_scoped_controls, which would presumably return the current scope.

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 clearly establishes the context: use this tool to retrieve the frozen control scope for an engagement, and it notes the role requirements (viewer or assigned auditor). It does not explicitly name alternative tools or state when not to use it, so it stops short of full routing guidance.

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