list_ssps

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

No annotations are provided, so the description must handle behavioral disclosure. It identifies the tool as a listing operation (implying read-only) but does not explicitly state that it has no side effects, require no special permissions, or explain what 'loaded' means. No contradictions with annotations exist, but transparency is minimal.

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 structured as a docstring with Args and Returns sections, making it easy to parse. However, it includes a redundant line about 'ctx: MCP server context (injected automatically)', which adds no value for an AI agent and could be omitted. Overall concise at ~6 sentences.

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 the tool is a simple list with two parameters and no output schema, the description adequately covers pagination behavior and return format (Page_Response dict with keys). However, it does not detail what 'items' contain or specify behavior when no SSPs are loaded. For a list tool, this is reasonably complete.

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 input schema has 0% description coverage for parameters. The description compensates by explaining 'offset' as zero-based pagination offset (default 0) and 'limit' as max items 1-100 (default 10), adding semantic meaning beyond the schema's type and default fields.

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 action ('List loaded OSCAL System Security Plans') and specifies the output nature ('summary metadata'). The verb 'list' and resource 'OSCAL System Security Plans' are specific and distinguish it from sibling tools that list other OSCAL objects (e.g., list_catalogs).

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?

No guidance is provided on when to use this tool versus alternatives like query_ssp or other list_* tools. The description does not mention preferred use cases, exclusions, or prerequisites for using the tool.

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