Pod Logs

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

No annotations exist, so the description carries the full behavioral burden. 'Still time-bounded' hints at a cap but never states the default window, what allowLongRange does, the default limit/sort, or the return format for a 35-parameter tool — a significant gap.

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?

Two tight, front-loaded sentences with no waste. However, the extreme brevity relative to a 35-parameter surface edges toward under-specification rather than efficient conciseness.

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?

With no annotations, no output schema, 54% param coverage, and 35 parameters, this description is far too thin. It gives no help navigating the large parameter set or understanding default/pagination behavior.

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?

At 54% schema description coverage, the description adds essentially zero parameter meaning beyond the schema. For a 35-param tool where nearly half the parameters are undocumented, the two-sentence description fails to compensate for the coverage gap.

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+resource: 'Last N log lines for a pod'. This distinguishes it from log-aggregation siblings, but the parenthetical '(still time-bounded)' is cryptic and the massive 35-param surface suggests it does far more than the stated 'last N lines'.

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?

Explicitly names preferred alternatives ('Prefer log_summary / search_logs for filters'), giving a when-not condition. The sibling names are abbreviated rather than exact IDs, but the routing intent is clear enough for an agent.

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