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

No annotations are provided, so the description must carry full behavioral burden. It discloses admin-restriction and out-of-band grant semantics. But it doesn't state whether grant is idempotent, what happens if the user already has a subscription, the default value effect, or side effects on billing. These gaps are notable for a mutation tool with zero annotation coverage.

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?

Two well-structured sentences with the admin/scope constraints front-loaded. No padding.

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?

No annotations, no output schema, 0% schema coverage, 3 parameters. The description covers the purpose and admin scope but leaves key behavioural and parameter details unspecified. For a privileged mutation tool, this is incomplete.

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 0%, and the description provides no parameter guidance. The 'days' parameter with a default of 30 is never explained, 'auth_token' is undocumented, and 'target_user_id' is only implied by the verb. With three parameters at 0% coverage, the description fails to compensate.

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?

Specific verb (accorde manuellement), specific resource (abonnement Iddet Plus), and explicit scope exclusion (hors flux de paiement Chariow). Distinguishes from siblings like mcp_create_actfile, mcp_register, mcp_cancel_subscription, which all manipulate other resources or state.

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?

Clarifies when to use: manual grant outside the Chariow payment flow. Explicitly restricts to admins via MCP_ADMIN_USERNAMES. Doesn't say when to prefer alternatives, but sibling-tool name and scope make the boundary clear.

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