marketplace_get_tool

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 says 'Get detailed information' but does not describe the return format, error cases, what happens when neither parameter is supplied, or any required permissions. This is a significant gap for a lookup 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 a single, front-loaded sentence with zero wasted words. It is appropriately concise for a simple read tool, though the brevity comes at the cost of missing contextual information.

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 tool has two optional parameters, no output schema, and no annotations, yet the description only offers a generic phrase. It fails to specify what 'detailed information' includes, how to identify the tool when both parameters are absent, or whether name or toolId is the more reliable identifier. This is insufficient for confident invocation.

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% (both 'name' and 'toolId' have basic descriptions), so the baseline is 3. The tool description adds no extra meaning about the parameters, such as mutual exclusivity, best practices, or consequences of omitting both.

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 a specific verb+resource ('Get detailed information about a specific tool'), conveying that this is a read operation for a single tool. It is distinguishable from sibling listing/discovery tools like marketplace_discover_tools and server_list_tools, though only via the name and the word 'specific'.

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 no guidance on when to use this tool versus alternatives such as marketplace_discover_tools, marketplace_search, or server_list_tools. It also does not explain whether the 'name' or 'toolId' parameter should be preferred or whether one is required.

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