eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no behavioral context about pagination defaults (25), cursor mechanics, or the parent-child relationship implied by object_slug. The claim 'all' contradicts the paginated nature of the endpoint.

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 brief (3 words) and front-loaded, but the word 'all' wastes the limited space by inaccurately suggesting non-paginated, global retrieval rather than scoped, paginated listing.

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?

Inadequate for a 3-parameter list endpoint with required parent filtering. Fails to explain the custom record concept, the mandatory object_slug relationship, or the paginated response structure despite lacking an output schema.

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?

Input schema has 100% description coverage documenting object_slug as parent resource ID and pagination controls. Description mentions no parameters, but with full schema coverage, baseline 3 is appropriate.

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?

States basic verb ('Get') and resource ('custom records'), but 'all' is misleading given pagination parameters (cursor, per_page) exist. Fails to mention the required parent resource scoping via object_slug. Distinguishes poorly from sibling get_custom_record (singular).

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?

Provides no guidance on when to use this versus the singular get_custom_record, create_custom_record, or update_custom_record. Does not mention that object_slug is required to scope the query to a specific parent object.

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