What can nable do

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds context beyond that: it mentions tailoring to connected services ('tailored to what you've connected') and explains the 'detailed' parameter's effect ('list the underlying tool names'). This provides useful behavioral detail without contradicting the annotations.

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 front-loaded with the primary purpose in the first sentence. It includes trigger phrases and examples, which are helpful but slightly redundant (e.g., multiple example queries). It remains appropriately sized for the tool's simplicity, staying under 150 words.

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 tool with a single optional boolean parameter and an existing output schema, the description is fully sufficient. It covers purpose, usage triggers, parameter behavior, and even situational guidance (post-connection). No critical information is missing.

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 schema has zero description coverage for the 'detailed' parameter. The description compensates by explicitly explaining its purpose: 'Pass detailed=True to also list the underlying tool names.' This adds meaningful semantic context beyond the schema's minimal definition.

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 'Show everything nable can do, tailored to what you've connected.' This is a specific verb ('Show') and resource ('everything nable can do'). It distinguishes itself from sibling tools like connect_aws or get_cost_summary by focusing on overall capabilities, and the usage examples reinforce its 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?

Explicitly provides when-to-use triggers: 'Call this when the user asks "what can you do?"...' and lists multiple example queries. It also gives a strong directive: 'Always call it right after a user connects their first account' to showcase new capabilities. No alternatives are mentioned, but the guidance is clear and actionable.

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