picus_get_latest_run_frameworks

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

Mentions raw API payload is returned as-is, providing some behavioral insight. No annotations exist, so description carries full burden; missing details on authentication, rate limits, side effects, or error conditions.

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, front-loaded with purpose, no fluff. Every sentence adds value: purpose first, then sibling comparison and behavioral note.

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?

Adequate for a simple tool with one parameter, but lacks output schema description (only says 'raw payload'). No context on prerequisites or error states. References sibling but does not fully explain workflow.

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?

Description adds no meaning beyond the schema for the sole parameter 'simulation_id'. With 0% schema description coverage, the description should compensate but does not explain the parameter's role or how to obtain it.

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?

Clearly states it retrieves the latest run's MITRE ATT&CK / Unified Kill Chain framework mapping. Distinguishes from sibling 'picus_get_run_frameworks' by specifying it is for the most recent run.

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?

Explicitly compares to sibling tool, indicating that this is the variant for the latest run. Provides context for when to use this tool, but lacks explicit when-not conditions or alternative usage scenarios.

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