ReftrixMCP

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the GDPR compliance framework context, which explains the nature of the audit logs, but doesn't disclose additional behavioral traits like rate limits, retention periods, or what specific processing activities are captured beyond the high-level GDPR reference.

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?

Extremely efficient bilingual format (Japanese/English) with zero waste. The two-sentence structure front-loads the action (search/query) and immediately qualifies the regulatory scope, delivering maximum information density without 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?

While the GDPR context is valuable, the description remains minimal for a compliance-focused tool with 5 optional parameters. It doesn't address the all-optional parameter design, expected result format, or pagination behavior beyond the limit constraint. Given the lack of output schema, additional context about return values would strengthen completeness.

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?

With 100% schema description coverage including examples (e.g., 'data.delete, page.analyze'), the schema carries the full burden of parameter documentation. The description provides no additional parameter semantics beyond the schema, warranting the baseline score of 3.

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 tool queries/searches audit logs (specific verb + resource) and adds valuable regulatory context by specifying GDPR Article 30 compliance records. However, it doesn't explicitly differentiate from the sibling 'accessibility.audit' tool, though the GDPR mention implicitly signals this is for data processing records rather than accessibility testing.

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 GDPR Art.30 reference provides implied usage context (use when needing records of processing activities for compliance), but lacks explicit when-to-use guidance, exclusions, or comparisons to alternatives like 'data.export' for data retrieval scenarios.

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