contribute_threat_signature

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

No annotations provided, and the main description only mentions 'anonymized' without details on hashing, effects, permissions, or response. Behavioral context relies on schema description for 'pattern' but is insufficient for a submission tool.

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?

Single sentence that is direct and to the point, with 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?

Without output schema or annotations, the description omits crucial details like return value, side effects, or submission confirmation, leaving the agent underinformed for a non-trivial operation.

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 descriptions cover 100% of parameters (pattern, category, severity) with meaningful text, but the main description adds no further context beyond the schema.

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 'Submit', the resource 'threat signature', and the destination 'cross-deployment intelligence mesh', making it distinct from sibling tools like 'predict_threats' or 'threat_intel_status'.

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 on when to use this tool versus alternatives such as 'deploy_honeypot' or 'detect_collusion'. The description does not specify prerequisites or context.

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