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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait—that it samples only ~4 seconds of logs—and the default container behavior. But it says nothing about auth/permissions, output volume limits, or whether lines are truncated, leaving mutation/read safety and result-shape context implicit.

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?

Three short sentences, front-loaded with the core capability, then the sampling behavior, then the parameter guidance. No filler or redundancy.

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 two-parameter read tool with no annotations and no output schema, the description covers purpose, sampling semantics, and the one ambiguous parameter. The main remaining gap is any indication of what the returned log lines look like or their volume, but overall it is sufficient to invoke correctly.

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 description coverage is 0%, so the description must compensate, and it does for the non-obvious parameter: container_select is explained as a managed_container_id with a cross-reference to get_app_details and a documented default. Only managed_app_id is left to inference, which is reasonable given the name and sibling naming conventions.

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?

States a specific verb and resource: 'Capture recent container log lines for an app.' No sibling tool in the provided list retrieves logs, so the agent can immediately distinguish this from the get_app_*/list_* family.

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?

Gives implicit context (log retrieval for a given app) and one useful operating instruction—omit container_select to target the app's first container. However, it offers no explicit when-to-use/when-not guidance or named alternatives among the sibling tools.

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