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

While the description mentions specific parameters for pay_booking, it does not explain how the 'data' parameter encodes actions or what the expected behavior for each action is. The input schema contradicts the described parameters, undermining trust.

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 structured as a list of actions with brief details, which is clear for the actions themselves. However, the '[Flattened action: update_nfse]' note is extraneous and adds noise.

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 the lack of output schema and the complexity of actions, the description is severely incomplete. It does not explain how to specify actions via the 'data' parameter, handle errors, or interpret results. The proliferation of sibling tools suggests this composite is redundant.

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 zero description coverage, and the description's parameter hints (e.g., 'association' for associate_account) do not match the schema's parameters (only 'data' and 'account'). This mismatch creates confusion rather than clarity.

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 lists multiple actions under 'Write financial operations', but the tool name and the '[Flattened action: update_nfse]' note create confusion about its primary purpose. It fails to distinguish from sibling tools that cover the same individual actions, such as feegow_financial_write_create_invoice.

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 only provides exclusion for destructive removals, but does not clarify when to use this composite tool versus the existing specialized write tools. The presence of sibling tools with identical action names makes the guidance misleading.

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