list_ssp_control_implementations

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

Describes the return format and pagination behavior, but does not explicitly state that the operation is read-only or mention any potential side effects; annotations are absent, so description carries full burden.

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 succinct, with a clear verb-resource statement, a brief explanation of the domain concept, and a well-organized parameter list. No superfluous 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?

Covers all necessary aspects for a list tool (what it lists, filtering, pagination, return format), though it does not mention prerequisites or error conditions; adequate for the tool's simplicity.

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?

Given 0% schema description coverage, the description fully documents all three parameters (parent_doc_uuid, offset, limit) with types, defaults, and purpose, adding significant value beyond the schema.

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 that the tool lists control-implementation elements within OSCAL SSP documents, which is a specific resource distinct from sibling tools like list_ssps or list_catalog_controls.

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?

Implies usage via parameter description (scoping to a single SSP), but does not explicitly describe when to use this tool vs alternatives or mention any exclusions.

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