feegow_dmed

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

No annotations provided. The description mentions HTTP GET, implying read-only, but does not disclose rate limits, error behavior, pagination, or the effect of parameters like query, offset, limit. Minimal behavioral context beyond the endpoint.

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 very short (one simple sentence plus a parenthetical). It front-loads domain and purpose but omits critical details, making it incomplete rather than efficiently concise.

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 7 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain data scope, filtering (dates, units), pagination, or typical usage patterns for a finance query tool.

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?

Schema description coverage is 57%. The description only repeats the CPF format already in the schema (11 digits). It adds no meaning for undocumented parameters (limit, offset, unidadeId) and does not explain the nested 'query' object behavior.

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 queries DMED data (tax receipts for declaration), which is a specific financial resource. The verb 'Consulta' (query) and resource 'DMED' are clear. However, it does not distinguish from sibling tools, though no direct sibling with 'dmed' exists.

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?

No guidance on when to use this tool versus alternatives (e.g., other financial tools like feegow_list_invoices). Only a constraint on CPF format is mentioned, but not when to avoid or fallback to other tools.

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