connection_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses almost nothing. It does not state whether the operation is read-only, what happens if the path does not exist, or any side effects. The description is essentially a shell that provides no behavioral information beyond the tool's name.

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 short, but this is under-specification rather than conciseness. The entire content is one sentence that offers no genuine explanation. It is not well-structured because it fails to communicate key information; the word count is minimal but not every word earns its place given that none of them provide substantive help.

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 that there is no output schema and the operation is a 'get' (presumably retrieving something), the description is completely inadequate. It does not explain what is returned, how the path maps to a connection, or any edge cases. The agent is left with no information to correctly invoke the tool or interpret results.

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 only one parameter ('path') but includes no description for it and the schema_description_coverage is 0%. The description mentions 'path (<class 'str'>): Operator path.' which is just repeating the type and adding 'Operator path' – a cryptic phrase that does not clarify what the path refers to. It adds too little meaning to compensate for the lack of schema descriptions.

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 is just 'Alias of conn.get.' with no elaboration on what the tool does. 'conn.get' is an undefined term and 'Alias of' is tautological; an agent cannot discern the actual purpose or the type of resource being retrieved. The name 'connection_get' suggests it fetches a connection, but the description does not confirm this or explain what 'conn' refers to.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like 'conn_create', 'conn_delete', and 'connection_create' exist, but the description does not specify when 'connection_get' is the right choice or contrast it with similar tools. No prerequisites or usage context are provided.

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