exploit_details

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only says 'Get exploit details.' It does not reveal whether the operation is read-only, what happens when an invalid ID is passed, or what the response contains. This is a significant gap for a tool with no other behavioral disclosures.

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 short, but it is under-specified rather than concise. The phrase 'Get exploit details' adds little value beyond the tool name and does not earn its place as a standalone description. It lacks structural organization and substantive content.

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 tool has one parameter, no output schema, and no annotations, the description is insufficiently complete. It does not state the expected input, the type of details returned, or any prerequisites. The surrounding sibling tools suggest the domain but the description leaves critical gaps for correct invocation.

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?

The schema has 0% description coverage for the single parameter edb_id. The description provides no explanation of what edb_id means (e.g., ExploitDB identifier), how to format it, or any constraints. It completely fails to compensate for the absence of parameter documentation.

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 'Get exploit details' identifies a clear action (get) and resource (exploit details), but it is vague and nearly restates the tool name. It does not specify the scope (e.g., by EDB ID) or what kind of details are returned, making it only marginally more specific than a tautology.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this tool retrieves details for a specific exploit by ID, nor does it contrast with related tools like exploit_search or exploit_copy. The agent is left to infer usage context.

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