stape_get_container

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

No annotations provided; description only says 'get' suggesting read-only but doesn't detail authentication needs, side effects, or what 'detailed information' encompasses. Carries full burden but offers minimal disclosure.

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?

Single sentence, 13 words, directly states purpose and key parameter usage. No redundancy or unnecessary detail.

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?

Adequate for a simple get operation with one parameter, but lacks description of return format or what 'detailed information' includes. No output schema to compensate, leaving some ambiguity.

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 describes containerId as 'Stape Container ID or Identifier', but description adds that it can be an API key, providing extra meaning beyond schema. Schema coverage is 100% but description adds useful context.

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 the verb 'get', the resource 'detailed information for a specific container', and the parameter (by container ID or API key). Distinguishes from siblings like stape_list_containers (which lists all containers).

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?

Implied usage: use this tool when you have a container ID or API key to retrieve details. No explicit when-not-to-use or comparison to alternatives (e.g., stape_list_containers for bulk listing).

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