get_methodology

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

No annotations exist, so the description must bear the burden. It indicates a read operation returning step-by-step approaches but does not disclose output format, limitations, or side effects. More detail on what 'returns' entails would improve 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 a single clear sentence that efficiently communicates purpose and scope. It is front-loaded and free of fluff, but could be slightly more structured (e.g., separating what it does vs. what it returns).

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?

For a simple tool with one parameter and no output schema, the description covers the main use case adequately. It states return type (methodology and checklists) and scope (specific types or general). Minor gaps: does not specify if output is per target type or list, nor the format (e.g., markdown).

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 single parameter target_type has 100% schema coverage with enum and description. The description reinforces the parameter's purpose but adds no new semantic detail beyond what the schema already provides. Baseline of 3 is appropriate.

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 structured bug bounty testing methodology and checklists for specific vulnerability types or general web app testing. The name aligns, and it is distinct from siblings like get_bounty_reports or get_cloud_security.

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 implies usage for testing methodology needs but does not explicitly contrast with siblings or provide when-not-to-use guidance. It lacks exclusion criteria or alternative recommendations.

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