FrelyMCP

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds auth context beyond that: no sign-in required, which is genuinely useful for an agent deciding whether it can call it unauthenticated.

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?

A single sentence that front-loads the content of the tool and closes with the constraint that matters most. No waste.

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 a no-param informational tool with no output schema, the description adequately conveys the scope of what is returned and the absence of side effects or auth needs. Slight gap in not relating it to the sibling tools an agent might confuse it with.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-related for the description to explain, and the empty schema is consistent with the description.

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 names the resource (Frely) and enumerates what the tool returns: what Frely is, what you can do with it, and how to connect an account. That is clear for an informational tool, though it does not explicitly differentiate itself from siblings like frely_list or models_list.

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?

"Needs no sign-in and changes nothing" implies the tool is safe to call at any point, which is implicit usage guidance. It never states when to prefer this over siblings such as frely_list or store, so an agent must infer the routing.

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

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

Annotations already cover read-only, idempotent, non-destructive and non-open-world behavior, so the bar is lower. The description adds genuinely new information: authentication is required, and unauthenticated invocation only returns signup/connect instructions rather than data — a meaningful behavioral caveat. It still says nothing about pagination or result size.

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 short sentences, front-loaded with what is listed before the authentication caveat. The second clause ('here it only explains how to sign up and connect') is slightly awkwardly phrased but still earns its place by preventing a false expectation of data.

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?

With no output schema, the description carries the burden of indicating what comes back, and the enumerated entity types largely do that. Combined with the annotation-derived safety profile and the disclosed auth requirement, an agent has enough to call and interpret this tool correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly implies a no-argument, account-scoped listing rather than suggesting any filter inputs.

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 a specific verb (List) and resource (Frely account contents) and enumerates the entity types returned: API keys, Credit, plans, orders, Creator items. It is distinguishable from siblings such as list_devices and models_list by scope, though it never explicitly names an alternative.

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 second sentence implies the usage condition: the call requires sign-in and otherwise degrades to signup/connection instructions. That is useful context, but no explicit when-to-use-vs-alternative guidance is given (e.g. how it differs from frely_about), so usage is only implied.

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

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is known. The description goes beyond that by disclosing the authentication requirement and the degraded behavior when unauthenticated (it explains sign-up/connection instead of returning devices), which is exactly the kind of context annotations cannot carry.

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 short sentences with no padding, and the core action is front-loaded before the caveat. The second sentence is terse to the point of ambiguity, but nothing is wasted.

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?

With no output schema, the description should ideally indicate what a device listing contains; 'what each can do' is the only hint. The auth caveat covers the main behavioral gap, but the phrasing about the tool 'only explaining sign-up' leaves the agent unsure what this call actually returns in the current 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?

The tool takes zero parameters, so the schema cannot be a source of ambiguity and the baseline is 4. There is nothing for the description to clarify about inputs, and it correctly makes no attempt to.

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?

Names a specific verb and resource ('List your computers linked to Frely') and adds scope ('what each can do'), which is enough to distinguish it from frely_about, frely_list and models_list. The trailing clause 'here it only explains how to sign up and connect' muddies whether it actually returns devices, slightly undercutting the otherwise clear purpose.

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?

It states a prerequisite ('Needs sign-in') and what happens when that prerequisite is unmet, which is real usage context. It never names an alternative tool or says when to prefer this over frely_list or frely_about, so routing guidance is only implied.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the tool requires sign-in and degrades to sign-up/connection instructions when the user is not authenticated.

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 short sentences, front-loaded with the core purpose, with no filler. The second sentence is a bit cryptic ('here it only explains how to sign up and connect') but remains brief.

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?

With no output schema, the description should say what the list contains (model names, IDs, agent entries) and how it relates to sibling listing tools; it only describes the auth behavior. Adequate but leaves a real gap for an agent deciding whether this returns usable model identifiers.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies a no-argument listing call and adds no misleading parameter expectations.

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 first sentence gives a specific verb and resource (list AI models and agents available through Frely), which is clearer than the sibling names frely_list or list_devices. However, it never differentiates itself from those siblings, and the trailing clause 'here it only explains how to sign up and connect' partially undercuts what the tool actually returns.

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 'Needs sign-in' note implies a usage condition: when unauthenticated, this tool explains sign-up/connection rather than returning models. That is a useful implied context, but no alternative tool is named and no explicit when-to-use vs when-not-to-use guidance is given.

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

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds valuable context beyond them: no sign-in is required, buying occurs externally, and results include prices and product links.

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 description is two tightly written sentences with no wasted text. The core purpose is front-loaded, followed by useful auth and purchase behavior.

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 a simple read-only catalog tool with rich annotations, the description is complete enough: it explains what the store contains, that prices and links are returned, and that no sign-in is needed. The optional category filter is well covered by the 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?

Schema coverage is 100%, so the category enum and its 'Only this category' meaning are already documented. The description lists the store categories but does not add syntax or filtering behavior beyond what the schema provides.

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 states a specific verb and resource: 'Show the public Frely Store'. It also enumerates the store's contents and scope, making it easy to distinguish from sibling tools such as frely_about, frely_list, list_devices, and models_list.

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?

It gives useful usage context by clarifying that the store is public, requires no sign-in, and that purchasing happens on the linked page. It does not explicitly compare this tool with sibling alternatives, so it stops short of full when/when-not routing.

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