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

Annotations only say readOnlyHint=false and openWorldHint=false, so the description carries most of the burden. It does convey that the tool executes another tool by name and passes a JSON arguments object, which is the core behavior. However, it does not disclose error behavior for unknown names, side effects of invoking arbitrary tools, or what the response looks like. The description is not contradictory to the annotations.

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?

Two short, purposeful sentences. The primary action is stated first, and the discovery prerequisite is included as a second sentence. No filler or redundancy.

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?

The description is enough for a basic dispatcher: name and arguments are clear, and tool_search guidance is given. However, with no output schema and minimal annotations, an agent might still wonder how to construct arguments for a specific tool and what happens on invalid names. Some additional detail about error handling and argument passing would improve completeness.

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 50%, with 'name' described in the schema. The description adds 'JSON arguments object', which reinforces the type and purpose of the arguments parameter, but does not clarify that arguments should conform to the named tool's own input schema. Since arguments is a generic free-form object, this is a meaningful gap, but the basics are covered.

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 verb 'Invoke', the resource ('Sunago Matrix MCP tool'), and the mechanism ('by its exact name with a JSON arguments object'). It also distinguishes itself from sibling tools by directing the agent to tool_search for discovery, making its role as a generic dispatcher clear.

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 explicit usage context: discover names via tool_search first, then invoke by exact name. It names the relevant sibling tool in the workflow. It does not explicitly state when not to use this tool in favor of direct sibling calls, but for a generic invoker this is a reasonable level of guidance.

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