mainwp_costs_add

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

No annotations are provided, increasing the descriptive burden. The description only says 'Add', implying creation but not disclosing side effects, required permissions, or whether the action is reversible. Minimal behavioral insight.

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 a single clear sentence with no wasted words. It could include a hint about Pro license requirement, but it is appropriately short.

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?

For a creation tool with 10 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, success/failure behavior, or how the cost entry is stored.

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?

All input schema properties have descriptions (100% coverage), so the schema already provides parameter semantics. The description adds no extra meaning beyond the schema.

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 the verb 'Add' and the resource 'cost entry', and distinguishes it from sibling tools like mainwp_costs_edit or mainwp_costs_delete. The context 'MainWP (Pro feature)' is specific.

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 (e.g., mainwp_costs_edit for modifications). No when-not or context for selection is given.

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