get_api_info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds no meaningful behavioral context beyond that. It does not describe response conventions, potential rate limiting, or the nature of the 'information' returned. There is no contradiction with the annotations, but the description contributes little independent 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 a single short phrase with no filler words. It front-loads the action and resource, and every word earns its place for a tool this simple.

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 no parameters, a safe read-only annotation, and an output schema present, the description covers the essential invocation context. It might have mentioned that this is the general discovery/metadata endpoint, but that gap is minor given the structured annotations and output schema.

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 tool has zero parameters, and schema description coverage is 100% by trivially covering everything. With no parameters to document, the description is not required to add meaning, and the baseline for zero-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 uses a specific verb, 'Get,' and names a concrete resource, 'basic API metadata and information,' which is distinct from the data-focused sibling tools like get_all_victims or get_group_info. It does not explicitly name a sibling to differentiate from, but the general 'API metadata' scope is enough to tell it apart from the specific data retrieval tools.

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?

There is no guidance on when to use this tool versus the many sibling tools, nor any mention of it as a discovery/capability-introspection endpoint. An agent gets no context about whether it should be called first, or how it relates to siblings like get_api_info or get_mitre_ttps.

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