browse_tool_usage

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the input parameters and basic purpose but omits important details such as read-only nature, data retention limits, pagination, or performance considerations. The agent is left with critical unknowns.

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?

Extremely concise: one-line purpose followed by a compact Args block. Every sentence is meaningful with 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?

With an output schema present (confirmed by context), the description does not need to detail return values. It covers the input parameters well. However, it lacks any mention of pagination, time range boundaries beyond days, or behavior when no logs exist. Slightly incomplete for a logging tool.

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?

Despite 0% schema description coverage, the description fully explains both parameters: 'days' with range 1-30, and 'tool_name' as optional filter. This adds practical meaning beyond the schema's default values alone.

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 the verb 'browse' and resource 'detailed tool usage logs', with specific detail on what is viewed ('when and how tools were used'). This distinguishes from sibling 'get_tool_usage_stats' which likely provides aggregated statistics rather than detailed logs.

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 explicit guidance on when to use this tool versus alternatives like 'get_tool_usage_stats'. The description does not mention any conditions or exclusions, leaving the agent to infer usage context.

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