fastbcp_info

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

The description declares the tool is 'Read-only, does not require database connectivity,' which adds behavioral context beyond the annotations (readOnlyHint, destructiveHint, idempotentHint). There is no contradiction with 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 extremely concise: three sentences covering purpose, usage of the action parameter, and safety. No extraneous information.

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?

While the description covers the different actions and their parameters, it does not describe the output structure or return format. Given no output schema, the description could provide more context on what the tool returns for each action to be fully 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?

With 100% schema coverage, all parameters have descriptions. The description adds value by grouping parameters with actions (e.g., 'action=parallelism requires source_type, has_numeric_key, table_size_estimate'), providing semantic understanding beyond the 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 clearly states the tool's purpose: 'Get information about FastBCP capabilities, parallelism recommendations, workflow guidance, or binary version.' It uses specific verbs ('get information') and resource ('FastBCP'), and distinguishes itself from sibling tools like fastbcp_execute_export by explicitly noting it is read-only and does not require database connectivity.

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 detailed usage context for each action type (formats, parallelism, workflow, version) and their required parameters. However, it does not explicitly contrast this tool with its siblings or state when not to use it, leaving room for improvement in guiding the agent towards alternatives.

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