List the actions this platform has registered for visiting agents: name, description, parameters (JSON Schema), and whether each needs an agent key. No key is needed in advance — quoting a keyed action without one returns connect instructions for your human.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses a key behavioral trait: no key is needed in advance, and quoting a keyed action without one returns connect instructions. This is beyond the basic 'list' behavior and gives the agent useful expectations about outcomes.
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 is informative and well-structured. It front-loads the core purpose ('List the actions...') and then adds the key behavioral note. No wasted words, though it could be more explicit about usage context.
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 is a simple discovery tool with no parameters and no output schema, the description covers the essentials: what it lists and a key behavioral nuance. It's complete enough for an agent to decide to call it and know what to expect. The only gap is lack of explicit routing to siblings, but that's not critical for a discovery tool.
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 the input schema is empty. The description doesn't need to explain any parameters, but it does explain what the returned list contains (name, description, parameters, key requirement), which adds value about the output. Since there are no params, baseline 4 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 states it lists registered actions with specific attributes (name, description, parameters, key requirement). It doesn't explicitly differentiate from sibling tools like 'about' or 'ask', but the verb and resource are clear enough for an agent to understand its purpose.
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 implies usage in a discovery context — an agent would call this to learn about available actions. However, it doesn't explicitly state when to use this versus siblings like 'about' or 'quote', nor does it mention any alternatives. The guidance is implicit but not strongly framed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly separate role: about explains the platform, ask answers questions, list_actions enumerates available actions, quote creates an execution quote, and confirm executes or polls a quote. There is little risk of selecting the wrong tool.
The action pair quote/confirm and list_actions follow an obvious imperative style, and all tools are short and readable. Minor inconsistency exists because about is a preposition rather than a verb, and list_actions uses an underscore while the others do not.
Five tools is appropriate for this domain: discovery, informational context, quoting, and confirmation are all represented. The surface is compact without feeling thin.
The platform provides a complete workflow for agents: learn about the platform, ask questions, list available actions, quote a specific action, and confirm or poll it. There are no obvious dead ends in the core flow.