mesh_describe_tool

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

With no annotations provided, the description carries the full burden. 'Inspect' implies a read-only, non-invoking operation, which is useful behavioral context, but the description does not explicitly state that the tool has no side effects, whether permissions are required, or how the default minification affects returned content.

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 front-loaded sentence with no wasted words. It states the action, the target, and the timing in one compact phrase.

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?

For a simple read-oriented inspection tool with a fully documented schema and no output schema, the description covers what the tool does and when to use it. A minor gap is that it says 'full JSON schema' without acknowledging that the default minify=true may prune some non-semantic content.

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 description coverage is 100%, so all three parameters are already well documented in the input schema. The description adds only the broad notion of inspecting a 'specific tool'; it does not add practical meaning beyond the schema for server, tool_name, or minify.

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 uses a specific verb and resource: inspect the JSON schema and parameter specifications of a specific tool. It is clear, but it does not explicitly distinguish itself from all siblings such as mesh_search_tools or mesh_status; it only indirectly contrasts with mesh_invoke_tool via 'before invoking it.'

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 phrase 'before invoking it' gives a clear usage context: call this to inspect a tool prior to execution. It does not explicitly name alternatives or exclusions, such as when to search for tools first versus describing a known tool, so it falls short of full when/when-not guidance.

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