get_suprsend_tenant

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

Description states 'Get' and 'Returns', implying read-only operation, but annotations include destructiveHint=true, which is contradictory. No explanation for the destructive hint is provided, severely undermining transparency.

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?

Description is three brief paragraphs with clear sections (what, when to use, when not, returns). Each sentence adds value, though the first paragraph could be more 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?

Despite lacking output schema, the description explains return content (settings, branding, custom properties) and clarifies what is not returned (preferences). Adequate for a get operation.

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?

Input schema covers both parameters with descriptions (100% coverage). Description adds context about returned fields but no additional parameter-level meaning beyond what schema provides. Baseline 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?

Description clearly states 'Get a tenant's settings, branding metadata, and custom properties by tenant_id', providing a specific verb and resource. It distinguishes from siblings like 'get_suprsend_tenants' (list) and 'get_tenant_default_preference' (defaults).

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?

Explicitly provides when to use (user references tenant by id) and when not to use, naming alternative tools 'get_suprsend_tenants' for enumeration and 'get_tenant_default_preference' for defaults.

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