freeagent_get_current_user

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

Description indicates a read-only operation (get), but with no annotations provided, it carries full burden. It lacks details on authentication requirements, potential failures, or what data is returned. Adequate but minimal.

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?

Single sentence, no unnecessary words. Front-loaded with verb and resource. Perfectly concise.

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 tool with no parameters and no output schema, the description is adequate but lacks detail on the return value shape. It doesn't explain what fields of the user are returned or the structure. Could be more complete.

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?

No parameters exist, so schema coverage is 100%. Description adds no parameter details, but none are needed. Baseline for zero parameters is 4, as the description correctly implies no input required.

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?

Description clearly states the verb 'Get' and the resource 'the currently authenticated user', which is specific and distinguishes it from sibling tools like freeagent_get_user (which requires a user ID) and freeagent_list_users (which lists all users).

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?

Description implies use this to retrieve information about the authenticated user, but provides no explicit guidance on when to use vs alternatives, such as freeagent_get_user for other users or freeagent_list_users for a list. No context on prerequisites or use cases.

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