get_active_profile

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses the key edge case: when no profile is active, it returns null plus a prompt message. It also enumerates the returned data categories, but it does not explain the meaning or format of 'connection status' or 'schema cache', nor discuss any other error or side-effect behavior.

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 substantive description is a single, compact sentence and is mostly front-loaded with the core purpose. However, the leading 'v5.0.0 (renamed from get_connection_status)' is historical/version metadata that does not help an agent select or invoke the tool, adding minor noise.

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?

For a zero-parameter status tool with no output schema and no annotations, the description covers the essential information: what is returned and the outcome when no profile is active. The main gap is that the exact meaning or shape of 'connection status' and 'schema cache' is not elaborated, but this is a minor omission for a simple getter.

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 and an empty schema, so there is no parameter documentation burden. The description appropriately focuses on return content and edge-case behavior, which is all that is needed for a parameterless getter.

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 action and resource: returning the currently active profile's name, full profile metadata, connection status, and schema cache. It distinguishes itself through the word 'active' from profile CRUD siblings, but it does not explicitly contrast with get_profile or list_profiles, so it stops short of full sibling differentiation.

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 intended use is implied by the phrase 'current active profile' and by the explicit null case when no profile is active. However, there is no direct guidance about when to choose this tool instead of get_profile, list_profiles, or use_profile, and no exclusions or alternative routing are provided.

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