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

With no annotations, the description carries the full burden and does disclose meaningful traits: a per-key rate limit with the 429 consequence, 'Idle $0, no LLM' cost behavior, tenant-scoped vs global-demo aliasing semantics, and that legacy domain keys are still accepted. It stops short of stating conflict/idempotency behavior when an alias already exists.

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 purpose is front-loaded, but the body is padded with marketing jargon ('E4 compounding thickens search boost', 'No invented premiums/prices', 'Managed SaaS compounding') and repeats the tenant-scoped compounding idea twice. Sentences do not each earn their place.

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 an 8-parameter write tool with no annotations and no output schema, the description covers rate limits, cost, and scope semantics, which is adequate. It omits what the response returns and what happens on duplicate/conflicting aliases, leaving gaps an agent would want before calling.

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 description coverage is 75%, so the schema already documents term, alias, boost, scope, domain, kind, and hints. The description's POST body listing largely restates those fields rather than adding syntax or format meaning; the one marginal addition is the scope-default rule, which the schema also states.

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 opening clause states a specific verb and resource — 'Add a synonym/alias (tenant-scoped or global demo)' — so the agent knows exactly what is created. It does not, however, reference the sibling pbx_dictionary (the read counterpart), so it loses the sibling-differentiation credit that would earn a 5.

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?

There is no explicit when-to-use guidance and no comparison to alternatives such as pbx_dictionary or pbx_facts. The only operational constraint given is the throughput cap ('≤60/hour/key → 429'), which is a limit, not usage direction.

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