generate_remediation_report

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that the tool returns a markdown-formatted prompt and mentions the report contents (remediated, partially remediated, required implementation). However, it does not disclose potential side effects, dependencies on prior threat model data, or whether the generation is purely computational, leaving gaps in behavioral 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 well-structured with a clear opening sentence, summary of report contents, and Args/Returns sections. It is slightly repetitive ('Generate a prompt' appears twice) but remains efficient and front-loaded. Every section earns its place, though the Args section for ctx could be omitted since it is not a user-facing parameter.

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 complete for a simple 0-parameter tool. It explains the output format (markdown prompt) and what the report covers. The output schema exists, so return values are already structured. Given the simplicity and good schema coverage, the description sufficiently covers the tool's context without needing extensive detail.

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?

With 0 parameters and schema coverage at 100%, the schema already fully accounts for parameters. The description adds a note about 'ctx' for logging and error handling, which is not in the schema but is internal MCP context. This is acceptable, and the baseline of 4 for 0-parameter tools applies.

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: 'Generate a prompt for LLM to create a comprehensive remediation report.' It uses a specific verb ('generate') and resource ('prompt'), and explicitly distinguishes its output (a prompt, not the report itself) from sibling tools like export_threat_model_with_remediation_status that directly export reports.

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 does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of when to choose this over export_threat_model_with_remediation_status or validate_threat_remediation. The context is implied but not stated, leaving the agent without clear selection criteria.

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