get_connection_status

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

No annotations are provided, so the description carries the full behavioral burden and mostly fails it. 'Get' weakly implies a read-only operation, but nothing states permissions, whether the connection_id must reference an existing connection, or what happens on an unknown ID.

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?

It is a single short, front-loaded sentence with no wasted words, but here the brevity is under-specification rather than efficiency. There is no structure to speak of because there is only one clause.

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?

With no annotations, no output schema, and 0% parameter coverage, the description is the only source of behavioral and return-value information, and it supplies none. Even for a simple single-parameter lookup, an agent is left guessing what 'metadata' contains and whether the call is safe or side-effect free.

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 0% for the sole required parameter, connection_id, and the description adds no meaning: it never says the parameter identifies which connection's metadata is fetched. Only the schema's 36-character length constraint hints at the identifier format, and that comes from the schema, not the description.

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 names a verb ('Get') and a resource ('connection metadata'), which is more than a tautology, but 'metadata' is undefined and it does not distinguish this tool from siblings like list_connections or get_operation_status. An agent cannot tell exactly what is returned or how this differs from those lookups.

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 when-to-use guidance, no preconditions, and no mention of alternatives such as list_connections for enumeration versus this per-connection lookup. The agent must infer usage entirely from the tool name and the single required parameter.

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