user_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get user profile information' without disclosing whether it returns the authenticated user's profile, any rate limits, authentication requirements, or possible side effects. The verb 'Get' implies read-only, but additional context is missing.

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, concise sentence that front-loads the action and resource. It contains no unnecessary words and is appropriately sized for a tool with no parameters and a simple purpose.

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 that there is no output schema and no annotation, the description should compensate by explaining what 'profile information' includes and how it differs from related tools. It fails to do so, leaving the agent uncertain about the return value and when to select this tool over siblings.

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 schema is empty. According to the rubric, a baseline of 4 is appropriate for tools with no parameters, since there is nothing for the description to explain beyond what the schema already clearly shows.

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 action ('Get') and resource ('user profile information') from Toshl Finance. It is specific enough to convey the tool's function, though it does not explicitly distinguish itself from the sibling tool 'user_summary', which might also provide user-related information. Thus it misses the 5-level requirement of differentiating from siblings.

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?

There is no guidance on when to use this tool versus alternatives like 'user_summary' or 'user_payment_types'. The description does not mention any use cases, prerequisites, or exclusions. This leaves the agent without direction for tool selection.

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