select_system_compliance_frameworks

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

No annotations are present, so the description must fully disclose behavior. It mentions the PRO tier requirement, but fails to describe mutational effects (e.g., whether selection replaces or adds frameworks), idempotency, or error conditions. This is insufficient for a mutation operation.

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 concise with one sentence and a tier requirement. It is front-loaded with the key action, but could be slightly more structured (e.g., separate purpose from requirement). No unnecessary words.

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 that the tool has three required parameters and no annotations, the description is too sparse. It does not explain the effect of selection, validation behavior, or how it interacts with related tools. An output schema exists but the description still lacks crucial context for a mutation tool.

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 coverage is 67%, with 'server_version' lacking a description. The description does not add any meaning beyond the schema: it does not clarify the format or purpose of parameters, nor does it compensate for the undocumented 'server_version' parameter.

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 verb 'select' and the resource 'compliance frameworks for a system'. It distinguishes from sibling tools like 'select_tag_compliance_frameworks' by specifying system-level scope, but could be more explicit about the action (assign/attach).

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 only usage guidance is the PRO tier requirement. No information is provided about when to use this tool versus alternatives like 'select_tag_compliance_frameworks' or 'list_compliance_frameworks'. There is no contextual advice on prerequisites or workflow steps.

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