btp_get_destination

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states the tool retrieves configuration details (URL, auth, proxy), implying a read operation, but does not clarify if it is read-only, any authentication requirements, potential side effects, or error conditions. The description is insufficient for an agent to understand the tool's behavior fully.

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 only one sentence, which is concise, but it omits critical information about parameters and usage. While brevity is appreciated, the lack of detail results in under-specification, making it less helpful than it could be.

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 lack of parameter descriptions, absence of an output schema, and minimal usage guidance, the description is incomplete. It does not explain how to identify the specific destination or what the returned configuration looks like, leaving significant gaps for an AI agent.

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 0% description coverage and the tool's description does not mention the two required parameters (args and kwargs) at all. It fails to explain how to specify the destination or how these parameters are used, leaving the agent without essential information to invoke the tool correctly.

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 verb 'Get', the resource 'full configuration of a specific destination', and specifies the included elements (URL, authentication, proxy). It distinguishes from the sibling tool 'btp_list_destinations' which lists destinations rather than retrieving a single destination's configuration.

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?

No guidance is provided on when to use this tool versus alternatives like btp_list_destinations. There is no mention of prerequisites, when not to use it, or how to specify the destination. The description is minimal and lacks usage context.

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