get_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 returned profile fields and implies an authenticated session, but it does not explicitly state that the operation is read-only, whether a valid session is required, or any other behavioral constraints. This is an adequate but minimal disclosure for a simple no-parameter read tool.

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 sentence that front-loads the verb and resource, then uses a colon to efficiently list the returned fields. Every word contributes meaning and there is no redundant or filler content.

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, read-only profile tool with an output schema available, the description covers the essential purpose and return contents. There are no hidden inputs or complex side effects, so nothing critical is missing for an agent to invoke it correctly.

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 takes zero parameters, so there are no parameter semantics to document. The description adds value by clarifying what the profile contains, which indirectly serves the same goal. Baseline 4 is appropriate for a parameterless tool.

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 a specific verb ('Get'), a specific resource ('logged-in user's profile'), and enumerates the returned fields (client code, name, email, exchanges, products, broker). This distinguishes it from all sibling tools, none of which target profile retrieval.

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 context of retrieving the logged-in user's profile is clear and the tool is unique among siblings, so no alternative routing is necessary. It does not explicitly say 'use after login', but the phrase 'logged-in user' implies the prerequisite without causing ambiguity.

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