list_model_card_export_jobs_sagemaker

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

No annotations are provided, so the description carries the full burden. It only says 'List Model Card Export Jobs', which implies a read-only operation, but it does not disclose other behavioral traits such as pagination, ordering, required permissions, or error behavior. The description is minimal and does not add context beyond the action itself.

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, front-loaded with the verb and resource, and contains no unnecessary words. It is appropriately concise for a simple list operation.

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's simplicity, single parameter, and the presence of an output schema, the short description is sufficient. The name and parameter make the purpose clear, and the output schema covers return values. There are no critical gaps, though a bit more context about usage could improve it slightly.

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 100% coverage with a clear parameter description ('The name of the SageMaker Model Card to list export jobs for'). The tool description does not add any parameter-specific meaning, but the schema fully documents the single parameter, so the baseline score of 3 is appropriate.

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 uses the specific verb 'List' with the resource 'Model Card Export Jobs' and scopes to 'a SageMaker Model Card'. This clearly distinguishes it from sibling tools like list_model_cards_sagemaker and list_model_card_versions_sagemaker, making the tool's purpose unambiguous.

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 states what the tool does but does not explicitly say when to use it versus alternatives. Usage is implied by the name and resource: use when you need to see export jobs for a specific model card. No alternatives, exclusions, or prerequisites are mentioned.

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