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

Beyond the openWorldHint annotation, the description discloses that this connection does not list the indexed servers and that the call is proxied to that server with its result returned here. That is useful behavioral context for an open-world proxy tool. It does not explain remote-tool side effects, failure modes, or latency, but the annotations already carry the safety profile for this local tool.

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 four compact sentences, front-loaded with the core action. Every sentence contributes either purpose, prerequisite, or proxying behavior. There is no repetition or filler.

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 annotations, a full input schema, and an output schema, the description covers the essential workflow and proxying behavior. The main remaining gap is that it does not explain how an agent should discover the remote tool's argument schema before passing arguments. Otherwise it is complete for this complexity level.

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 coverage is 100%, so the schema already documents slug, tool, and arguments. The description adds valuable context by explaining that slug and tool should come from a prior search_records or recommend_records call. It does not describe the arguments object, but the schema handles that adequately.

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 states a precise verb and target: run a tool on a public MCP server from the AgentStatus Index. It also distinguishes this tool from the sibling tools search_records and recommend_records by explaining the prerequisite sequence. An agent can tell exactly what this tool does without opening the schema.

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?

It explicitly says to call search_records or recommend_records first, then pass the resulting slug and tool. This names the alternatives and the condition for using this tool. The guidance is direct and leaves no ambiguity about the required workflow.

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