edubase_post_integration_keys

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

The description says 'rotate' but does not disclose behavioral traits beyond the annotations. It omits side effects (e.g., old keys invalidated immediately), required permissions, or rate limits. Annotations provide readOnlyHint: false, which is consistent, but no additional context is added.

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 extremely concise (5 words) and front-loaded. While it could include more detail, it earns a high score for brevity without redundancy.

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 tool has an output schema (not shown) and one parameter. The description is minimal: it states the action but doesn't explain the return value or post-conditions. Given the simplicity, it is adequate but not fully 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?

Schema coverage is 100% (one parameter fully described). The description adds no extra meaning beyond the schema's 'integration identification string'. Baseline is 3 per high coverage.

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 'Rotate integration keys/secrets' clearly states the action (rotate) and the resource (integration keys/secrets). It is specific and distinct from sibling tools like edubase_get_integration_keys (retrieve) and edubase_post_integration (create).

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no explicit context. The annotation destructiveHint: false is present, but no usage direction is given.

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