scf_get_engagement_presentation

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'read — viewer, or assigned auditor'. It adds that the output is organized by the framework's own structure, but it does not disclose error/access-failure behavior or response shape, so it adds only moderate context beyond the annotation.

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 sentence that front-loads the core action and packs the distinguishing behavior into a parenthetical and colon. It is compact, though the 'read — viewer, or assigned auditor' phrase is somewhat dense and could be clearer.

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 read tool with three required parameters and a fully documented schema, the description is mostly sufficient. It gives a high-level idea of the return (controls organized by framework structure), but because there is no output schema it could say more about exact return format, and it does not provide explicit routing guidance relative to sibling tools.

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%, so all three parameters (org_id, engagement_id, framework) are already documented in the schema. The description merely echoes the framework constraint and does not add new syntax or parameter-level detail beyond what the schema provides.

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 action and resource: get the engagement's scope rendered in a chosen framework's native structure. The phrase 'as an auditor reads them' and 'one of its frameworks' helps distinguish it from generic scope/control-list siblings, though it never explicitly names an alternative.

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 when-to-use or when-not-to-use guidance, and no sibling alternatives are named. The 'natively in one of its frameworks' wording implies its niche versus similar tools like scf_get_engagement_scope or scf_list_scoped_controls, but the agent must infer this.

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