set_competencies

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

With no annotations, the description carries full burden. It discloses the critical destructive behavior: 'Replaces any existing competencies entirely.' This is sufficient for a simple store operation, though it omits details like output or idempotency.

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 two sentences, front-loaded with the verb-object pair, followed by the key behavioral note. No filler or 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?

Despite low complexity (one parameter), the description lacks schema guidance due to 0% coverage. It does not compensate with parameter explanations, leaving the agent without enough context to construct valid input. Sibling tools like get_competencies could help but are not referenced.

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?

Given 0% schema description coverage, the description must explain parameters but does not. It only says 'Store the user's competency framework' without describing the structure of the competencies array. The agent cannot infer required fields or format from the description alone.

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 identifies the tool's action ('Store the user's competency framework') and the specific resource. It also explicitly states that it replaces existing competencies entirely, distinguishing it from incremental update tools like update_achievement.

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 implies that this tool is for full replacement rather than incremental updates, but it does not explicitly state when to use it versus alternatives (e.g., set_goals or add_achievement). No direct comparison or contraindications are provided.

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