get_slack_manifest

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

No annotations are provided, so the description carries the full burden. It only states that the tool 'gets' the manifest, implying a read operation, but provides no details about authentication requirements, rate limits, or the nature of the returned data. This is minimal disclosure.

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 extremely concise—one sentence with a prerequisite note. It is front-loaded with the most critical information and contains no redundant words. Every part is valuable.

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 no parameters and no output schema, the description is brief but sufficient for a simple retrieval operation. However, it lacks context about what the manifest contains or the format of the response, which could be useful for an AI agent.

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 zero parameters, the baseline is 4. The description adds no parameter information beyond what the empty input schema provides, but there is no need for additional parameter semantics.

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 action (Get), the resource (Slack app manifest), and the source (from Metabase). It distinguishes itself from the sibling tool 'get_slack_app_info' by specifying 'manifest', so purpose is unambiguous.

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 explicitly notes a prerequisite ('Requires Metabase Pro'), which helps users know when the tool is applicable. However, it does not provide guidance on when to use this tool versus the related sibling 'get_slack_app_info', nor does it specify conditions for use.

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