Listar assinaturas

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

Description discloses the read-only nature (matches readOnlyHint annotation) and adds specific behavior: subscriber data is masked. Provides more context than annotations alone.

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?

Single sentence effectively conveys purpose, resource, and returned fields. Could be slightly more structured (e.g., bullet points), but it is concise without being terse.

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 simple listing tool with one optional parameter and no output schema, the description covers the returned data and read-only nature. Annotations provide open world hint, making it sufficiently complete.

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 only parameter (limit) has 100% schema coverage with a clear description in the schema. The tool description adds no additional parameter information, so baseline score is appropriate.

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?

Description clearly states the tool lists subscriptions (recurrences) with specific fields (product, status, value, periodicity, masked subscriber data) and identifies the account context (autenticada ZuckPay). Differentiates from siblings like listTransactions and listProducts by resource.

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?

Description does not explicitly state when to use or when not to use. It implies read-only usage with 'Somente leitura' but lacks guidance on alternatives or prerequisites.

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