get_suprsend_tenant

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

Description describes a read-only get operation, but annotations include destructiveHint=true, which contradicts the non-destructive nature implied. The description does not address this contradiction or explain any potential side effects.

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?

Concise with clear sections: purpose, usage guidelines, returns. Only 4 sentences, no fluff, and front-loaded with the core functionality.

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?

Covers purpose, usage context, and return values adequately for a simple get tool with full schema coverage. However, lack of clarification on the destructiveHint contradiction leaves a gap in behavioral understanding.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; it only mentions 'by tenant_id' which aligns with the required parameter, but no additional details on format or behavior.

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 'Get a tenant's settings, branding metadata, and custom properties by tenant_id', specifying the verb and resource, and distinguishes from siblings like get_suprsend_tenants and get_tenant_default_preference by mentioning the identifier.

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 includes 'When to use' and 'When NOT to use' sections, naming alternatives (get_suprsend_tenants for enumeration, get_tenant_default_preference for defaults), providing clear context for tool selection.

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