acedatacloud_get_user_info

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 key behavioral traits: it operates on the 'current platform credential' (no parameters needed) and returns a specific set of fields. This is sufficient for a simple read-only getter; it does not mention error or edge cases, but the scope is small and clearly communicated.

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 three sentences long and each earns its place: purpose, returned fields, and usage context. It is front-loaded with the action, then provides concrete value for the agent without any filler or repetition of structured schema information.

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 tool with an output schema, the description covers all essential aspects: what it does, what it returns, and when to use it. The output schema exists and the description supplements it with the credential context and a real-world example. No further detail is needed for correct selection and invocation.

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 is empty. The description correctly notes that the account is determined by the current credential, making parameter semantics non-applicable. The baseline for 0 params is 4, and the description reinforces that no arguments are 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?

The description clearly states the action: 'Get the current authenticated AceDataCloud account's user profile.' This is a specific verb plus resource, and it distinguishes itself from sibling tools by focusing on the user account rather than sites, domains, or billing. It also lists the exact fields returned, removing ambiguity.

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?

Provides a concrete use case: 'Useful for constructing personalized content (e.g. inviter_id referral links).' This gives clear context for when to invoke the tool. It does not explicitly mention alternatives or when-not-to-use, but no sibling tool offers equivalent user-profile functionality, so exclusions are unnecessary.

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