get_consumer_profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds meaningful behavioral context by specifying that results are aggregated across sessions and agents and by listing the included data fields, going beyond the annotations.

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, focused sentence that front-loads the purpose and then lists the return fields compactly. Every part adds information, with no filler or repetition of the tool name or annotations.

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 low-complexity, single-parameter read-only tool, the description provides a solid summary of the return payload since there is no output schema. The only minor gap is the lack of detail on field types or formats, but the enumerated fields are sufficient for an agent to understand what the tool returns.

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 consumer_key is fully described in the schema, including normalization expectations and its equivalence to agent_sessions.consumer_key. With 100% schema description coverage, the tool description does not need to add parameter details, so the baseline of 3 applies.

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 uses a specific verb and resource ('Retorna o perfil agregado de um consumidor') and enumerates the returned fields, making the tool's function clear. It conveys a distinct scope ('cross-session, cross-agent') that separates it from session-specific siblings like get_session_history, but it does not explicitly name or contrast any sibling.

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 description implies when to use the tool: when an aggregated, cross-session, cross-agent profile of a single consumer is needed. It provides no explicit guidance on when not to use it or which alternative to choose (e.g., list_consumers, list_consumer_sessions, get_session_history).

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