clearLogs

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

Discloses destructive nature thoroughly: 'Permanently deletes', 'cannot be undone', 'use with caution'. With no annotations, the description fully informs the agent of behavioral traits.

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 with warnings and bold formatting. Each sentence adds critical information; no wasted words.

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 simple, destructive tool with one parameter and no output schema, the description covers all essential behavioral and safety aspects. Context from siblings and schema is well-supported.

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 coverage is 100%, so baseline is 3. Description does not add extra meaning beyond what schema provides for the profile_id parameter. The association with the profile is implicit.

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 'Permanently deletes all query logs for this profile', using a specific verb and resource. It distinguishes from sibling tools like getLogs (read) and deleteProfile (delete profile itself).

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?

Safety note 'Only use with designated test profiles' provides clear context for when to use. Warning about irrevocability guides caution, but lacks explicit alternatives or when-not-to-use scenarios.

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