get_active_profile

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

No annotations are provided, so the description carries the full burden. It discloses the tool's read-only behavior (implied by 'Get'), but lacks details on permissions, error conditions, or return format. For a zero-parameter tool, this is minimally adequate, but more behavioral context would improve transparency.

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, clear sentence with no wasted words. It is front-loaded with the core purpose, making it highly efficient and easy to parse for an AI agent.

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's simplicity (zero parameters, no output schema, no annotations), the description is complete enough for basic use. It specifies what is retrieved ('currently active profile ID'), but could be enhanced by mentioning the return type or format, especially since no output schema is provided.

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 the input schema has 100% description coverage (though empty). The description does not need to add parameter details, so it appropriately focuses on the tool's purpose without redundancy. A baseline of 4 is justified as no parameters are present.

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') and the specific resource ('the currently active profile ID'), making the purpose unambiguous. It effectively distinguishes this tool from siblings like 'ac_getProfileById' (which retrieves a specific profile by ID) and 'set_active_profile' (which sets rather than gets).

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 description implies usage context by specifying 'currently active', suggesting this tool is for retrieving the profile ID that is currently in use. However, it does not explicitly state when to use this versus alternatives like 'ac_getProfileById' or 'ac_listProfiles', nor does it provide exclusions or prerequisites for use.

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