issue_api_key

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

No annotations provided, but the description includes the rate limit (5 per day) and key format, offering partial behavioral insight. Lacks details on side effects like old key invalidation or permissions.

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?

Three sentences, each earning its place: action, use cases, rate limit. Front-loaded and no unnecessary 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?

Given no parameters and no output schema, the description covers key format, use cases, and rate limit adequately. Missing response format details, but tool simplicity allows minor gaps.

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 has zero parameters (empty object), so description adds no parameter info. Baseline for 0 params is 4; no additional value needed beyond schema completeness (100%).

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 it issues a fresh ta_data_* API key for the current tenant, with specific use cases like pasting into /add-database or configuring integration, distinguishing it from sibling database tools.

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 provides explicit use cases ('useful for pasting...') and a rate limit, but does not mention when not to use or alternatives, though none are obvious among siblings.

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