perseus_tooltrim

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

Discloses read-only behavior ('Read-only') and the aggregated nature of stats mode, adding context beyond the readOnlyHint annotation. No contradictions.

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 concise sentences that front-load the core purpose and immediately provide usage conditions. Every sentence adds value with no redundancy.

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?

Given no required params, a schema coverage of 100%, and presence of output schema, the description fully covers the tool's functionality, both modes, and constraints.

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. The description adds clarifying context for the 'full' parameter ('For full tool metadata') and implies the 'stats' parameter returns aggregated counts, enhancing understanding beyond schema types.

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?

The description uses a specific verb ('return') and resource ('filtered toolset metadata and usage statistics'), clearly distinguishing this tool from siblings like perseus_list or perseus_tool that may handle related but different data.

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 states when to use ('to understand what tools are available and how they are being used') and provides conditional guidance for full metadata vs stats mode. Lacks explicit when-not-to-use or alternative tool references.

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