Create or update service

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

With no annotations, description should reveal behavior but only says 'Manage'. No mention of idempotency, error handling, or 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?

Single sentence; concise but one-size-fits-all. No structure or hierarchy; could be reorganized.

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 output schema, no annotations, and 0% param descriptions, description fails to provide sufficient context for usage, parameter roles, or expected behavior.

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?

0% schema coverage; description mentions deliverables, officialUrl, status, featured but ignores id, seo, slug, order, title, summary, eyebrow. Incomplete coverage for 11 parameters.

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?

Description says 'Manage a service' which is vague; does not clearly state create/update despite title. Lists some aspects but lacks a precise verb. Differentiates from siblings like delete_service but not sharply.

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?

No guidance on when to use this tool vs siblings (e.g., save_category). No context about prerequisites or alternatives.

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