get_tool_catalog

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

With no annotations, the description carries the behavioral burden, and 'Return' clearly implies a read-only, side-effect-free operation. It also indicates the content scope ('Agent-facing Vivado MCP capability matrix and tool groups'), useful context for an agent. It does not mention whether a session or environment detection is required, but the zero-parameter schema reduces that risk.

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 filler. Every word adds meaning, and it is appropriately sized for a zero-parameter metadata lookup tool.

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?

Given the low complexity (no parameters), the presence of an output schema, and the straightforward read-only nature, the description is complete enough for an agent to select and invoke the tool correctly. No additional prerequisites or edge conditions are needed.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The description focuses on what the returned catalog contains, which is sufficient given the empty input 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 uses a specific verb ('Return') and names a clear resource: the Agent-facing Vivado MCP capability matrix and tool groups. This distinguishes it from operational siblings like run_synthesis or get_timing_summary, and even from other discovery tools like get_agent_workflows, because it is about tool groups/capabilities.

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 implies this is a discovery/catalog tool for understanding available agent-facing capabilities, but it does not explicitly say when to use it versus siblings such as get_agent_workflows or get_agent_scenarios. No exclusion criteria or alternative guidance is provided.

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