ods_get_connection_info

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

The description is consistent with the readOnlyHint annotation and adds the 'current connection' framing, which implies it reports state rather than modifying it. However, it does not disclose any additional behavioral traits such as behavior when no connection exists or whether the result reflects locally cached vs. live connection data. The annotation already covers the core safety profile, so this is adequate but not rich.

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 a single, front-loaded sentence with no filler or repetition. For a zero-parameter getter tool, this is appropriately concise and structurally efficient.

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 tool has no parameters, has a readOnlyHint annotation, and has an output schema, the description covers the essential purpose without needing to explain return values. It is complete enough for an agent to select and invoke the tool correctly, though a small note about requiring an active ODS connection could add context.

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 tool has zero parameters, so there is no parameter semantics burden for the description to carry. The schema is already fully complete and the description does not need to explain any inputs.

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 uses a specific verb ('Get') and resource ('current ODS connection information'), making it clear this is a read-only informational tool. It is distinguishable from siblings like ods_connect and ods_disconnect because it retrieves state rather than changing it, though it does not explicitly name those alternatives.

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 given about when to call this tool instead of ods_connect_env_list or ods_connect. The intended use is only implied by the phrase 'current ODS connection information'; there are no explicit conditions, prerequisites, or exclusions.

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