spider_signals

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool returns detection signals and fix principles, implying a read-only operation. However, it does not detail output format, side effects, or prerequisites, limiting transparency.

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 two sentences in Korean, tightly packed with purpose and usage guidance. No redundant information; every sentence adds value.

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?

The tool has 3 optional parameters, no output schema, and no annotations. The description covers what it returns and when to use it, but omits output structure and behavioral details like idempotency or rate limits. Adequate for basic use but not fully complete.

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 description coverage is 67% (tag and klass have descriptions; tier lacks one). The description adds that parameters are filters, which aligns with schema. However, the missing description for tier enum values (king/mid/baby) is a gap that the description does not fill.

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 clearly states the tool returns detection signals and fix principles for empirical bug classes, with filtering by klass/tier/tag. It distinguishes from siblings like spider_plan (planning) and spider_pull_corpus (pulling corpus) by emphasizing execution after planning.

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?

The description explicitly says 'after planning, execute these signals as-is to collect evidence,' providing clear context for when to use the tool. It also mentions filtering parameters. However, it does not explicitly exclude use cases or name alternatives among siblings.

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