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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds no behavioral context beyond restating the GET HTTP verb. It does not disclose filtering behavior, pagination, authentication needs, or what activity data is returned.

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 front-loaded sentence containing the action and endpoint, with no wasted words. It is concise and easy to parse, though it is so sparse that it sacrifices useful detail.

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 list tool with no output schema and undocumented parameters, this description is incomplete. The agent cannot infer parameter semantics, result shape, or when this tool is more appropriate than the many sibling list/create/get tools.

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 input schema has two optional parameters (query and account) with 0% description coverage, and the description does not explain either parameter. The agent is left with no semantic information about what these parameters do, their expected formats, or how they affect the request.

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 'Buscar atividades' (search activities) and includes the GET endpoint, making the action and resource explicit. It is distinguishable from sibling tools like datacrazy_activities_get, create, patch, and delete since this is the list-style operation, though it does not clarify whether it returns all activities or supports scoped search.

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 provides no guidance on when to use this tool versus alternatives such as datacrazy_activities_get or datacrazy_leads_activities_list. It does not mention exclusions, preferred contexts, or how the optional query/account parameters should influence selection.

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