wise_profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description's only additional contribution is the word 'authenticated', implying it resolves credentials from the connection rather than parameters. It says nothing about what profile fields come back or any rate-limit/error 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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity reflects under-specification rather than tight editing of richer 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 simple one-parameter read tool with no output schema, the agent still does not know what the profile response contains (name, email, locale, IDs) or how it relates to wise_accounts. Annotations cover safety, but the return-value gap is unaddressed since no output schema exists to compensate.

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?

Schema description coverage is 0% for the single optional api_key parameter, so the description carries the burden and does not address it at all. It never says whether api_key overrides the configured credential or is required in some deployments, leaving an agent to guess at an authentication-affecting parameter.

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?

States a specific verb and resource: 'Get the authenticated Wise user profile.' An agent can tell this is a read of the current user's own profile. However, it does not distinguish itself from the nearby siblings wise_accounts or wise_exchange_rates, which also read Wise account-level data, so the boundary is left implicit.

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 when-to-use or when-not-to-use guidance, and no mention of wise_accounts as the alternative for balance/account data. The only implicit signal is the word 'authenticated', which suggests it uses configured credentials rather than a user identifier.

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