get_salesbot_by_id

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

With no annotations provided, the description carries the burden of indicating that this is a read-oriented lookup rather than a mutation. The verb 'Busca' clearly communicates retrieval of details, which is the core behavioral trait. It does not detail error behavior or authorization, but for a simple get-by-id tool this is acceptable.

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 Portuguese sentence conveys the essential purpose and scope without any filler. Every word contributes meaning.

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 straightforward get-by-id tool, the description plus a fully documented schema provides enough to invoke it correctly. The main omission is not explicitly relating this tool to the sibling get_salesbots listing tool or mentioning the role of client_slug in the description, but the schema covers that.

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 already documents both parameters with 100% coverage, so the baseline is 3. The description reinforces that the ID is the lookup key but does not add meaning beyond the schema.

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 ('Busca os detalhes'), the specific resource ('um Salesbot específico'), and the lookup method ('usando o ID'). This distinguishes it from the sibling tool get_salesbots, which is a plural listing 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?

The description implies this should be used when fetching a single Salesbot by ID, and 'específico' hints at contrast with listing. However, it does not explicitly mention when to use get_salesbots instead or provide any when-not-to-use guidance.

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