scf_get_engagement_presentation

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

With no annotations supplied, the description carries the full behavioral disclosure burden and does signal that this is a read-oriented operation for a viewer or assigned auditor. However, it does not describe return format, error behavior, pagination, or what happens when the framework is not one of the engagement's own.

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 compact sentence with the core action front-loaded: 'Get the engagement's scope presented natively in one of its frameworks.' The trailing phrase 'as an auditor reads them' is slightly redundant, but overall there is little wasted text.

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 operation with three well-documented parameters, the description conveys the purpose, the read-only audience, and the framework-native organization. It is less complete about the exact response shape and does not explicitly differentiate this from scf_get_engagement_scope, and there is no output schema to close that gap.

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%, and each parameter already has meaningful guidance such as 'obtain from scf_list_organizations' and 'must be one of the engagement's own frameworks'. The description adds context about why framework matters, but it does not need to compensate for missing schema documentation, so the baseline 3 is appropriate.

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 states a specific verb and resource: retrieving the engagement's scope as a framework-native presentation. It also explains the distinguishing shape of the result — 'SCF controls organised by that framework's own structure, as an auditor reads them' — which separates it from a plain scoped-control list or a generic engagement fetch.

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 explicit guidance about when to use this tool versus closely related siblings such as scf_get_engagement_scope or scf_list_scoped_controls. The phrase 'read — viewer, or assigned auditor' hints at an audience/permission context, but it does not state when to choose this tool instead of another.

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