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

Annotations declare readOnlyHint and idempotentHint, and the description aligns by saying 'consulta' (query) and mentions it's not confidential data. It also adds legal context about data controller and LGPD, which is extra but not directly about the tool's runtime behavior. It doesn't discuss pagination, limits, or response format. The description adds some but not extensive transparency, so a 3 is appropriate.

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 front-loads the purpose clearly but then adds lengthy legal and business disclaimers (hosting, payment, LGPD) that are not directly about the tool's usage. It could be trimmed to focus on the query capability and parameters, but it's not excessively long.

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?

Given 4 parameters with zero schema coverage and no output schema, the description must explain usage. It does not describe how parameters interact, which are optional, or what the response looks like. It provides business context but lacks technical detail needed to actually make a query.

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 schema provides no descriptions for the four parameters (ie, razao_social, nome_beneficio, codigo_beneficio), and the description does not mention any of them. There is zero guidance on how to use these parameters, whether they are mutually exclusive, or what formats they expect. The description adds no semantic value beyond the parameter names, which are already in the schema. Since schema coverage is 0%, the description fails to compensate.

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 tool's purpose: 'Consulta Credenciamentos' for SEFAZ MT, and indicates it queries official Brazilian sources. It names the entity and the domain. It could be more specific about what 'credenciamentos' refers to (e.g., tax accreditations?), but it is adequate for understanding the primary function.

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 does not provide guidance on when to use this tool versus alternatives, nor does it suggest typical use cases. It mentions no prerequisites beyond prepaid credit buys, but doesn't explain how to structure queries or when this tool is appropriate. There are no sibling tool comparisons.

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