Get AsyncAPI Spec Metadata

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

With no annotations provided, the description carries full burden for behavioral transparency. It lacks details like whether the operation is read-only, any rate limits, or the behavior when the version parameter is omitted. It only states what is returned, not how the tool behaves.

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 with no unnecessary words. It efficiently conveys the core purpose. However, it could be slightly more structured (e.g., listing the metadata fields) without adding bulk.

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 has one optional parameter and no output schema, the description adequately states the return values (source, version, cache, size). But it does not explain the output format or clarify how the version parameter interacts with the 'latest' default. Sibling tools are not referenced for context.

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 description adds value beyond the schema by noting the version parameter defaults to 'latest from master' and giving an example value ('3.0.0'). However, the description's phrase 'latest... specification' could be seen as conflicting with the parameter's role in retrieving non-latest versions.

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 returns metadata (source, version, cache, size) for the latest AsyncAPI specification. The verb 'Return' and resource 'metadata' are specific. However, it does not explicitly differentiate from sibling tools like get_asyncapi_spec_section or list_asyncapi_spec_versions, which have distinct purposes.

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 its siblings. It does not mention that the optional version parameter overrides the 'latest' default, nor does it suggest alternative tools for other tasks like retrieving a spec section or listing versions.

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