Ludus FastMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns detailed information and lists output keys, but doesn't cover critical aspects like whether it's a read-only operation, potential rate limits, authentication needs, or error handling. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 well-structured and front-loaded with the core purpose. It efficiently explains the return value and provides a clear example. While slightly verbose in listing output keys, each sentence adds value, and there's no redundant information.

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's simplicity (0 parameters, no annotations, no output schema), the description is adequate but has gaps. It covers the purpose and output structure well, but lacks behavioral context (e.g., safety, performance) and usage guidelines. For a read operation in a complex sibling environment, more guidance would improve completeness.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on output semantics by detailing the return structure (adversary_profiles, defender_profiles, siem_types, use_cases), which adds value beyond the schema. This compensates well for the lack of an output 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?

The description clearly states the tool's purpose: 'List all available adversary and defender profiles with descriptions.' It specifies the verb ('List') and resource ('adversary and defender profiles'), and distinguishes it from siblings like 'apply_adversary_profile' or 'apply_defender_profile' by indicating it's for listing rather than applying. However, it doesn't explicitly differentiate from other list tools like 'list_ranges' or 'list_templates', which keeps it from a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., before applying profiles), or compare it to other list tools in the sibling set. The example shows basic usage but lacks contextual advice, leaving the agent to infer usage scenarios.

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