get_agent_scenarios

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Return' implies a read-only operation, but the description does not explain whether scenario_id filters to a single scenario or whether omitting it returns all scenarios, leaving meaningful behavior undisclosed.

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?

A single front-loaded sentence with no filler. Every word contributes to the core meaning, making it efficient and easily parseable.

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 is simple with one optional parameter and an output schema, so the description is nearly sufficient. Missing parameter semantics and usage differentiation are the main gaps, but an agent could likely call it correctly based on the clear verb and obvious scenario_id name.

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 0% and the only parameter, scenario_id, is not mentioned in the tool description. The parameter name hints at filtering, but the description adds no semantic value beyond the raw schema.

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 specific verb ('Return') and resource ('reusable Subagent validation scenarios') with clear domain context ('Agent-facing Vivado MCP acceptance'). It doesn't explicitly differentiate from siblings like get_agent_workflows, but the resource noun is specific enough to convey the tool's purpose.

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 'for Agent-facing Vivado MCP acceptance' gives context but no explicit when-to-use or when-not-to-use direction. It also names no alternatives, so an agent must infer when to choose this over get_agent_workflows or get_tool_catalog.

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