eduframe-mcp

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

The description adds no behavioral context beyond the annotations (which indicate read-only, idempotent, non-destructive). It fails to describe return value structure, error conditions (e.g., record not found), or the relationship between the parent object_slug and the record id.

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?

While brief (3 words), this constitutes under-specification rather than efficient conciseness. The single sentence fails to earn its place by providing actionable information beyond the tool name itself.

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 the presence of easily confused sibling tools (get_custom_records vs get_custom_record) and no output schema, the description should clarify scope (single vs list) and return behavior. It provides the minimum possible information, leaving critical gaps in context.

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, the baseline is 3. The description 'Get a custom record' adds no additional parameter context beyond what the schema already documents for 'object_slug' and 'id'.

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 'Get a custom record' is tautological, essentially restating the tool name. It fails to distinguish from sibling tool 'get_custom_records' (plural/list) or clarify that this retrieves a single specific record by ID versus listing multiple records.

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 provided on when to use this tool versus alternatives like 'get_custom_records' or 'get_custom_object_by_object_slug'. No mention of prerequisites or required context (e.g., needing the object_slug from a parent custom object).

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