Get Container

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds the 'owned' qualifier, which is a meaningful restriction beyond annotations, clarifying that only containers owned by the user are retrievable.

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, 'Get one owned Container/List.', with no redundant words. It communicates the purpose efficiently and is appropriately front-loaded.

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?

For a one-parameter get operation, the description covers the core purpose but is minimal. It does not describe return values, error behavior, or whether archived containers are included, and no output schema exists to fill the gap.

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 description does not mention container_id or explain its semantics. With 0% schema description coverage, the description fails to compensate, leaving the parameter meaning entirely to the parameter name and format uuid.

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 tool gets a single owned Container/List, using the specific verb 'Get' and identifying the resource. It distinguishes itself from sibling list/create/update/delete container tools by specifying 'one' and the ownership qualifier.

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 implies usage for retrieving a single container by ID, but it does not explicitly contrast with list_containers or other get_* tools. There is no mention of when not to use it or alternatives, leaving the guidance at an implied level.

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