public_access_portal_invoices

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

The description only says it returns HTML page content but does not disclose authentication requirements, pagination behavior (though the page parameter hints at it), or what happens on error. No annotations exist to offset this lack of detail.

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 sentence but lacks essential information, making it under-specified rather than concise. It earns no value from brevity because it omits critical details.

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 no annotations, no output schema, and 0% parameter coverage, the description fails to provide a complete understanding of the tool's behavior. It ignores pagination, authentication, and return value details.

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 0%, and the description adds no meaning to the two parameters (connection and page). The agent must guess the purpose of these parameters from their names and defaults, which is insufficient.

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 gets a list of portal invoices and returns HTML page content. It mentions the endpoint (/my/invoices) and distinguishes from sibling tools like public_access_portal_home by specifying invoices.

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 like public_access_portal_orders or public_access_portal_purchases. No conditions or prerequisites are mentioned, leaving the agent to infer usage.

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