list_profile_imports

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explains that imports have synthetic positional IDs, describes pagination parameters (offset, limit with defaults and range), and details the return structure (Page_Response with specific keys). This provides solid transparency beyond minimal expectations.

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 well-structured with a brief introductory sentence, an explanatory note about imports, and clear Args/Returns sections. It is concise without unnecessary detail, earning its place sentence by sentence.

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 lack of output schema, the description fully specifies the return format (Page_Response with keys: items, total, offset, limit, hasMore). It also describes parameter behavior and context, making the tool fully understandable for an AI agent.

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 0%, so the description must fully explain parameters. It does: parent_doc_uuid is optional for scoping, offset defaults to 0, limit defaults to 10 with a range of 1-100. This adds significant meaning beyond the bare schema types.

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 'List import elements within OSCAL Profile documents', specifying the verb (list) and resource (import elements). It distinguishes from siblings by mentioning 'within OSCAL Profile documents', implying this tool lists sub-elements of profiles, unlike 'list_profiles' which lists profiles themselves.

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 description mentions that parent_doc_uuid can scope results to a single profile, but does not explicitly state when to use this tool vs alternatives like list_profiles or list_catalogs. No exclusions or alternative tools are named, leaving the agent to infer usage context.

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