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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds behavioral guidance by instructing 'Present the returned link exactly', which tells the agent not to modify or reformat the result. This is meaningful context beyond the annotations, though the term 'noticed' remains ambiguous.

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 zero fluff. The main purpose is front-loaded, followed immediately by the most instructive example and a crisp output-handling directive. 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 3-parameter tool with a rendered output schema and safety annotations, the description covers the essential decision points: integration vs. MCP, the Wispr Flow special case, and exact presentation of the result. A minor gap is not explaining mcp_url selection behavior, but the schema fully covers that.

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 the schema documents all parameters. The description adds value by giving a concrete example mapping for Wispr Flow (target='integration', source='wispr-flow'), which clarifies how the enum values should be combined, and by implying the returned value is a link to be used as-is.

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 ('Get') and resource ('connection or management experience for an integration or MCP server'), and explicitly differentiates between the two target types. The Wispr Flow example further pins down the exact usage, making the tool's purpose unmistakable and distinct from any sibling tool.

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 clear context on when to use the tool (for retrieving connection/management links) and includes a concrete parameter mapping for Wispr Flow. It does not explicitly state exclusions or alternatives, but no sibling tool appears to overlap with this function, so the guidance is sufficient.

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