get_mitre_ttps

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and external data access. The description adds the Pro-tier API key requirement and mentions it is part of a comprehensive profile, but does not disclose other behaviors like rate limits, pagination, or error handling. This adds some context beyond annotations but not rich behavioral detail.

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 sentence that front-loads the requirement and states the core function. The phrase 'as part of its comprehensive Pro-tier intelligence profile' adds minimal value and could be trimmed, but overall it is efficient and well-structured.

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?

With one well-documented parameter and an output schema present, the description covers the essential purpose and constraints. It lacks explicit guidance on when to use this tool versus siblings, but the existence of an output schema and the simplicity of the tool make it reasonably complete for an agent to call correctly.

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?

Schema description coverage is 100% – the 'group' parameter already has a clear description with examples. The tool description does not add any additional semantics beyond what the schema provides, so baseline 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 identifies the resource (a ransomware group's MITRE ATT&CK TTPs, exploited CVEs with CVSS scores, and tooling) and the action (get). It distinguishes itself from siblings like get_group_info or get_iocs by naming specific data types. The scope is unambiguous and not a tautology.

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 states a prerequisite (Pro tier, requires RANSOMWARE_LIVE_API_KEY) which is a usage constraint, but it does not explicitly say when to use this tool versus alternatives (e.g., get_group_info for general info, get_iocs for indicators). The usage context is implied by the data it returns, not explicitly contrasted with siblings.

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