get_demo

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

Annotations already indicate readOnlyHint=true and openWorldHint=false. Description adds context that the tool does not execute or control a PC, which is helpful beyond annotations. No contradictions.

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 sentences with no wasted words. Purpose is stated first, then critical non-behavior, then usage conditions, then output handling. Every sentence earns its place.

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-only retrieval tool with 2 enum parameters and no output schema, the description provides all necessary context: what it does, when to call, what to do with the result, and what it is not. Complete.

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% with clear descriptions for both parameters (demo_id enum, format enum). Description adds no new parameter detail beyond reinforcing that demo_id comes from list_demos, which is already implied.

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?

Clearly states 'Return one showcase run contract' with specific verb and resource, and explicitly distinguishes from execution ('Does NOT execute the demo or control a PC'). Differentiates from sibling 'list_demos' by describing what it returns.

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?

Provides explicit when-to-use ('Call after list_demos when you know the demo_id') and action-oriented guidance based on client capability ('If the client can run shell, offer the command; if chat-only, show the card'). Also warns against misuse ('Do not replace this with a slow MCP click loop for solver demos').

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