get_recent_logs

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

No annotations provided; description only states it 'gets recent log lines' without disclosing behavioral traits like whether it returns only new logs, includes timestamps, or requires permissions. Minimal behavioral context despite carrying full burden.

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?

Brief and to the point: main action in first sentence, then parameter details listed clearly. No redundant or wasted text.

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?

Output schema exists so return value explanation is optional. Tool is simple with 3 optional params, but 'recent' is undefined (e.g., time range). Adequate for basic use but could be more precise.

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 lacks descriptions for all 3 parameters (coverage 0%), but the main description provides concrete examples for category ('LogTemp', 'LogNet'), severity levels, and default count (50). This adds significant value beyond schema.

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 uses specific verb 'get' and resource 'recent log lines', and mentions optional filters (category/severity). Clearly distinguishes from siblings like search_logs and tail_log by specifying 'recent' and listing filter examples.

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 (e.g., search_logs, tail_log, get_log_stats). Does not state prerequisites or when not to use it.

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