get_rs0n_methodology

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

No annotations are provided, so the description carries full burden. It describes the content (four pillars) but does not disclose the behavior (e.g., return format, whether it's a summary or full text, any side effects). For a read-only retrieval of static content, this is adequate but not rich.

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?

Two sentences: first introduces the specific resource, second emphasizes its importance and lists content. Every sentence is useful, no fluff.

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 description is adequate for a simple retrieval tool but misses details about the output format and does not cover all possible input values (missing overview and skills). Given the absence of an output schema, this is a gap.

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 100% coverage with a description for the 'pillar' parameter. The tool description adds context by listing four pillars, but omits two enum values (overview, skills) and does not explain their meanings. The parameter is simple, so the description adds marginal value.

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 retrieves a specific methodology from a named source (rs0n's DEFCON 32 workshop) and lists the pillars. It distinguishes itself as the 'PRIMARY methodology' for testing, but does not explicitly differentiate from the sibling 'get_methodology' tool.

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 this should be the primary methodology guiding all testing, implying it should be used first. However, it does not mention when to use alternatives or when not to use this tool.

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