vibekit_app_logs

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

No annotations are provided, so description should disclose behavioral traits; it only says 'for debugging and monitoring' but doesn't mention that it's a read operation, any auth requirements, or potential performance impact. Lacks transparency.

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?

Very concise at 6 words, but front-loads purpose effectively. Could include structured details like usage context without becoming verbose.

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?

No output schema and no annotations; description fails to explain return format, pagination, or what constitutes 'logs'. For a 2-parameter tool with possible output volume, more context is needed.

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 100%, so baseline is 3. Description adds no extra meaning beyond the schema; the 'lines' parameter default (100) is not mentioned, nor any format details.

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?

Description clearly states 'Get application logs' with a specific verb and resource, and the sibling tools like vibekit_get_app and vibekit_agent_history suggest different purposes, so it distinguishes adequately.

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?

No guidance on when to use this tool versus alternatives like vibekit_agent_history or vibekit_app_env, nor any prerequisites or context. The description is minimal.

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