get_suprsend_tenants

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

The description states 'List all tenants' indicating a read-only operation, but the annotations include destructiveHint: true, which contradicts the tool's behavior. Annotations also include readOnlyHint: true and idempotentHint: true, adding to the inconsistency.

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 three sentences long, each serving a purpose: stating purpose, providing usage context, and describing return. It is front-loaded and contains no wasted words.

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?

The description explains the return format ('id and properties') despite lacking an output schema. It does not cover pagination or workspace specificity, but for a simple list tool this is adequate. The contradiction in destructiveHint reduces completeness.

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 coverage is 100% with both parameters having descriptions. The description repeats 'default 100' for limit, adding no new meaning beyond the schema. Baseline score of 3 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?

The description clearly states 'List all tenants in the workspace', providing a specific verb and resource. It distinguishes itself from siblings by mentioning its use to discover tenant_ids before calling get_suprsend_tenant or upsert_suprsend_tenant.

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 explicitly says 'Use to discover tenant_ids before calling get_suprsend_tenant or upsert_suprsend_tenant', giving clear usage context. However, it does not explicitly state when not to use this tool or mention alternatives beyond the two siblings.

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