cumulus_profile

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

No annotations are supplied, so the description carries the full burden, and it does disclose the login requirement — a genuinely useful behavioral trait. It leaves unstated that the operation is a safe read and what happens if the session is unauthenticated, so the disclosure is partial rather than complete.

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?

Two terse clauses, front-loaded with the resource and its payload, with the auth constraint appended. Nothing is wasted, though the extreme terseness is part of why the 'full' parameter goes unexplained.

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?

An output schema exists, so return-value detail is not required, and the auth note covers the main call precondition. For a tool with one undocumented parameter and no annotations, however, the description should have explained the 'full' flag and distinguished the tool from neighboring profile and loyalty endpoints.

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 single parameter 'full' has a boolean type, a default and zero schema description coverage, and the description never mentions it. The agent is told which fields come back but not what toggling 'full' changes, which is the only ambiguity an agent faces when invoking this 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 names a specific resource and enumerates the returned attributes: card number, memberships, lifestage. That is enough to distinguish it from data-only siblings such as cumulus_points or cumulus_wallet, though it never explicitly contrasts itself with the adjacent my_profile tool.

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?

'Requires login' implies an authentication precondition, which is a small piece of context. Beyond that there is no guidance on when to call this instead of my_profile, cumulus_wallet or cumulus_points, and no explanation of when the 'full' variant is appropriate.

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