perseus_tool

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

With no annotations, the description carries full burden but provides no behavioral traits. It does not disclose side effects, permissions needed, or what constitutes an 'allowlist', leaving the agent blind to critical operational details.

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?

The description is very short but suffers from under-specification rather than conciseness. It lacks essential details that would justify its brevity, resulting in a loss of utility.

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 the abstract nature of the tool and the absence of output schema or annotations, the description is severely incomplete. It fails to explain the allowlist mechanism, tool invocation details, or any constraints, making it nearly unusable.

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?

Although schema coverage is 100%, the description adds no value beyond the schema. The param 'args' is described as 'Arguments for @tool directive', which is cryptic and unexplained. The description does not clarify expected format or usage context.

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 states it runs an allowlisted external tool, but the resource is abstract and not specific. It does not differentiate from sibling tools which are domain-specific (e.g., perseus_date, perseus_drift), leaving the agent unsure when to use this generic tool versus the specialized ones.

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 is provided on when to use this tool compared to alternatives. The description lacks any context about prerequisites, scenarios, or exclusions, making it difficult for an agent to select appropriately.

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